Method for transmitting and receiving downlink data in wireless communication system, and device for same

ABSTRACT

A method for transmitting and receiving downlink data in a wireless communication system, and a device for same are disclosed. Specifically, the method includes the steps of: receiving setting information; receiving downlink control information (DCI); and receiving a plurality of transmission occasions of the same transport block based on the DCI, wherein a repetition scheme based on time division multiplexing (TDM) is set based on the setting information, the DCI includes a time domain resource assignment field, resource allocation in a time domain for a first transmission occasion may be determined based on the time domain resource assignment field of the DCI, and the resource allocation in the time domain for a second transmission occasion may be determined based on the resource allocation in the time domain for the first transmission occasion.

CROSS-REFERENCE TO RELATED APPLICATIONS

Pursuant to 35 U.S.C. § 119(e), this application is a continuation of International Application No. PCT/KR2020/010924, filed on Aug. 14, 2020, which claims the benefit of U.S. Provisional Application No. 62/886,947, filed on Aug. 14, 2019, No. 62/891,241, filed on Aug. 23, 2019, No. 62/896,014, filed on Sep. 5, 2019, and KR Application No. 10-2019-0099951, filed on Aug. 14, 2019, No. 10-2019-0107789, filed on Aug. 30, 2019, No. 10-2019-0122727, filed on Oct. 3, 2019, No. 10-2019-0127364, filed on Oct. 14, 2019, No. 10-2019-0143016, filed on Nov. 8, 2019, the contents of which are all hereby incorporated by reference herein in their entirety.

TECHNICAL FIELD

The present disclosure relates to a wireless communication system, and more particularly, to a method for transmitting and receiving downlink data based on multiple transmission reception points (TRPs), and a device for supporting the same.

BACKGROUND ART

Mobile communication systems have been developed to provide a voice service while ensuring the activity of a user. However, in the mobile communication system, not only a voice, but also a data service is extended. At present, there is a shortage of resources due to an explosive increase in traffic, and users demand a higher speed service. As a result, a more advanced mobile communication system is required.

Requirements for a next-generation mobile communication system should be able to support the acceptance of explosive data traffic, a dramatic increase in the per-user data rate, the acceptance of a significant increase in the number of connected devices, very low end-to-end latency, and high-energy efficiency. To this end, various technologies are researched, which include dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, device networking, and the like.

DISCLOSURE Technical Problem

The present disclosure proposes a method for receiving, by a UE supported by multiple transmission reception points (TRPs), downlink data in a wireless communication system.

Specifically, the present disclosure proposes a method for configuring a scheme (e.g., eMBB operation or URLLC operation) in which multiple TRPs perform cooperative transmission.

Further, the present disclosure proposes a method for configuring a specific scheme among various schemes related to a URLLC M-TRP operation.

Further, the present disclosure proposes a method for configuring the number of times at which transmission occasions corresponding to the same transport block are repeatedly transmitted by considering a TDM based URLLC M-TRP operation.

Further, the present disclosure proposes a method for configuring a resource of a time domain in which transmission occasions corresponding to the same transport block are repeatedly transmitted by considering the TDM based URLLC M-TRP operation.

Further, the present disclosure proposes a method for configuring a field (e.g., TCI field) of DCI by considering an M-TRP operation.

The technical objects of the present disclosure are not limited to the aforementioned technical objects, and other technical objects, which are not mentioned above, will be apparently appreciated by a person having ordinary skill in the art from the following description.

Technical Solution

A method for receiving, by a user equipment (UE), downlink data in a wireless communication system according to an embodiment of the present disclosure may include: receiving configuration information, a repetition scheme based on time division multiplexing (TDM) being configured based on the configuration information; receiving downlink control information (DCI), the DCI including a time domain resource assignment field; and receiving a plurality of transmission occasions of the same transport block based on the DCI, in which resource assignment in a time domain for a first transmission occasion may be determined based on the time domain resource assignment field of the DCI, and resource assignment in the time domain for a second transmission occasion may be determined based on the resource assignment in the time domain for the first transmission occasion.

Further, in the method according to an embodiment of the present disclosure, a size of a second resource in the time domain for the second transmission occasion may be determined based on a size of a first resource in the time domain for the first transmission occasion, and the size of the first resource and the size of the second resource may be equal to each other.

Further, in the method according to an embodiment of the present disclosure, the first resource and the second resource may be constituted as a unit of 2, 4, or 7 OFDM symbols.

Further, in the method according to an embodiment of the present disclosure, a first symbol of the second resource may be positioned from a last symbol of the first resource after a specific number of symbols.

Further, the method according to an embodiment of the present disclosure may further include receiving information on the specific number of symbols.

Further, in the method according to an embodiment of the present disclosure, in the method, the first resource and the second resource may be positioned in concatenation with each other in the time domain.

Further, in the method according to an embodiment of the present disclosure, the DCI may further include a transmission configuration indication (TCI) field, and a plurality of TCI states may be indicated based on the TCI field, and the number of the plurality of transmission occasions may be determined based on the number of plurality of TCI states.

Further, in the method according to an embodiment of the present disclosure, a first TCI state may correspond to the first transmission occasion and a second TCI state may correspond to the second transmission occasion.

Further, in the method according to an embodiment of the present disclosure, the first transmission occasion and the second transmission occasion may be received in one slot.

Further, in the method according to an embodiment of the present disclosure, the DCI may further include a redundancy version (RV) field, and an RV value of the first transmission occasion and an RV value of the second transmission occasion may be differently configured based on the RV field.

A user equipment (UE) for receiving downlink data in a wireless communication system according to an embodiment of the present disclosure may include: one or more transceivers; one or more processors; and one or more memories storing instructions for operations executed by the one or more processors and connected to the one or more processors, in which the operations may include receiving configuration information, a repetition scheme based on time division multiplexing (TDM) being configured based on the configuration information, receiving downlink control information (DCI), the DCI including a time domain resource assignment field, and receiving a plurality of transmission occasions of the same transport block based on the DCI, in which resource assignment in a time domain for a first transmission occasion may be determined based on the time domain resource assignment field of the DCI, and resource assignment in the time domain for a second transmission occasion may be determined based on the resource assignment in the time domain for the first transmission occasion.

A method for transmitting, by a base station (BS), downlink data in a wireless communication system according to an embodiment of the present disclosure may include: transmitting, to a user equipment (UE), configuration information, a repetition scheme based on time division multiplexing (TDM) being configured based on the configuration information; transmitting, to the UE, downlink control information (DCI), the DCI including a time domain resource assignment field, and transmitting, to the UE, a plurality of transmission occasions of the same transport block based on the DCI, in which resource assignment in a time domain for a first transmission occasion may be determined based on the time domain resource assignment field of the DCI, and resource assignment in the time domain for a second transmission occasion may be determined based on the resource assignment in the time domain for the first transmission occasion.

A base station (BS) for transmitting downlink data in a wireless communication system according to an embodiment of the present disclosure may include: one or more transceivers; one or more processors; and one or more memories storing instructions for operations executed by the one or more processors and connected to the one or more processors, in which the operations may include transmitting, to a user equipment (UE), configuration information, a repetition scheme based on time division multiplexing (TDM) being configured based on the configuration information, transmitting, to the UE, downlink control information (DCI), the DCI including a time domain resource assignment field, and transmitting, to the UE, a plurality of transmission occasions of the same transport block based on the DCI, and resource assignment in a time domain for a first transmission occasion may be determined based on the time domain resource assignment field of the DCI, and resource assignment in the time domain for a second transmission occasion may be determined based on the resource assignment in the time domain for the first transmission occasion.

A device according to an embodiment of the present disclosure may include: one or more memories and one or more processors functionally connected to the one or more memories, in which the one or more processors may be configured to control the device to receive configuration information, receive downlink control information (DCI), and receive a plurality of transmission occasions of the same transport block based on the DCI, and a repetition scheme based on time division multiplexing (TDM) may be configured based on the configuration information, the DCI includes a time domain resource assignment field, resource assignment in a time domain for a first transmission occasion may be determined based on the time domain resource assignment field of the DCI, and resource assignment in the time domain for a second transmission occasion may be determined based on the resource assignment in the time domain for the first transmission occasion.

In one or more non-transitory computer-readable media storing one or more instructions according to an embodiment of the present disclosure, the one or more instructions executable by one or more processors may include instructions for instructing a user equipment (UE) to receive configuration information; receive downlink control information (DCI); and receive a plurality of transmission occasions of the same transport block based on the DCI, and a repetition scheme based on time division multiplexing (TDM) may be configured based on the configuration information, the DCI may include a time domain resource assignment field, resource assignment in a time domain for a first transmission occasion may be determined based on the time domain resource assignment field of the DCI, and resource assignment in the time domain for a second transmission occasion may be determined based on the resource assignment in the time domain for the first transmission occasion.

Advantageous Effects

According to an embodiment of the present disclosure, an operation scheme of multiple TRPs can be configured to a UE and the UE can perform an operation corresponding thereto.

Further, according to an embodiment of the present disclosure, the number (the number of repetition times of transmission occasions) of transmission occasions corresponding to the same transport block in TDM based M-TRP URLLC transmission can be configured.

Further, according to an embodiment of the present disclosure, a shifting symbol and/or RV values can be configured for each transmission occasion.

Further, according to an embodiment of the present disclosure, a resource region can be determined in which the transmission occasions corresponding to the same transport block are received in the TDM based M-TRP URLLC transmission.

Further, according to an embodiment of the present disclosure, a conventional DCI field can be configured or interpreted to suit an M-TRP operation.

Effects which may be obtained from the present disclosure are not limited by the above effects, and other effects that have not been mentioned may be clearly understood from the following description by those skilled in the art to which the present disclosure pertains

DESCRIPTION OF DRAWINGS

The accompany drawings, which are included to provide a further understanding of the present disclosure and are incorporated on and constitute a part of this specification illustrate embodiments of the present disclosure and together with the description serve to explain the principles of the present disclosure.

FIG. 1 is a diagram illustrating an example of an overall system structure of NR to which a method proposed in the present disclosure may be applied.

FIG. 2 illustrates a relationship between an uplink frame and a downlink frame in a wireless communication system to which a method proposed in the present disclosure may be applied.

FIG. 3 illustrates an example of a frame structure in an NR system.

FIG. 4 illustrates an example of a resource grid supported by a wireless communication system to which a method proposed in the present disclosure may be applied.

FIG. 5 illustrates examples of a resource grid for each antenna port and numerology to which a method proposed in the present disclosure may be applied.

FIG. 6 illustrates physical channels and general signal transmission.

FIG. 7 illustrates an example of a downlink transmission/reception operation.

FIG. 8 illustrates an example of an uplink transmission/reception operation.

FIG. 9 is a flowchart illustrating an example of a DL DMRS procedure.

FIGS. 10A and 10B illustrate an example of a transmission/reception method for improving reliability using transmission in multiple TRPs.

FIG. 11 illustrates an example of a configuration of a shifting symbol between transmission occasions.

FIG. 12 illustrates an example of a transmission occasion repeatedly transmitted in one slot.

FIG. 13 illustrates an example of resource allocation for repeated transmission in a time domain proposed in the present disclosure.

FIG. 14 illustrates an example of slot unit repeated transmission based on a transmission occasion structure defined in a first slot in order to prevent repeated transmission by exceeding one slot.

FIG. 15 illustrates an example of resource allocation to a transmission occasion exceeding a slot boundary according to a method proposed in the present disclosure.

FIG. 16 illustrates an example of a time domain resource allocation method when a transmission occasion exceeding a slot boundary occurs to which the method proposed in the present disclosure may be applied.

FIG. 17 illustrates an example of application of a DMRS pattern to repeatedly transmitted transmission occasions.

FIG. 18 illustrates an example of a signalling procedure performing data transmission/reception between a network side and a UE in a situation of multiple TRPs to which methods and/or embodiments described in the present disclosure are applicable.

FIG. 19 illustrates an example of an operation flow chart of a UE performing data transmission/reception to which methods and/or embodiments described in the present disclosure are applicable.

FIG. 20 illustrates an example of an operation flowchart of a BS performing data transmission and reception to which a method and/or an embodiment proposed in the present disclosure may be applied.

FIG. 21 illustrates a communication system applied to the present disclosure.

FIG. 22 illustrates a wireless device which may be applied to the present disclosure.

FIG. 23 illustrates a signal processing circuit for a transmit signal.

FIG. 24 illustrates another example of a wireless device applied to the present disclosure.

FIG. 25 illustrates a portable device applied to the present disclosure.

MODE FOR DISCLOSURE

Reference will now be made in detail to embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. A detailed description to be disclosed below together with the accompanying drawing is to describe exemplary embodiments of the present disclosure and not to describe a unique embodiment for carrying out the present disclosure. The detailed description below includes details to provide a complete understanding of the present disclosure. However, those skilled in the art know that the present disclosure may be carried out without the details.

In some cases, in order to prevent a concept of the present disclosure from being ambiguous, known structures and devices may be omitted or illustrated in a block diagram format based on core functions of each structure and device.

Hereinafter, downlink (DL) means communication from the base station to the terminal and uplink (UL) means communication from the terminal to the base station. In downlink, a transmitter may be part of the base station, and a receiver may be part of the terminal. In uplink, the transmitter may be part of the terminal and the receiver may be part of the base station. The base station may be expressed as a first communication device and the terminal may be expressed as a second communication device. A base station (BS) may be replaced with terms including a fixed station, a Node B, an evolved-NodeB (eNB), a Next Generation NodeB (gNB), a base transceiver system (BTS), an access point (AP), a network (5G network), an AI system, a road side unit (RSU), a vehicle, a robot, an Unmanned Aerial Vehicle (UAV), an Augmented Reality (AR) device, a Virtual Reality (VR) device, and the like. Further, the terminal may be fixed or mobile and may be replaced with terms including a User Equipment (UE), a Mobile Station (MS), a user terminal (UT), a Mobile Subscriber Station (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), a Wireless Terminal (WT), a Machine-Type Communication (MTC) device, a Machine-to-Machine (M2M) device, and a Device-to-Device (D2D) device, the vehicle, the robot, an AI module, the Unmanned Aerial Vehicle (UAV), the Augmented Reality (AR) device, the Virtual Reality (VR) device, and the like.

The following technology may be used in various radio access system including CDMA, FDMA, TDMA, OFDMA, SC-FDMA, and the like. The CDMA may be implemented as radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. The TDMA may be implemented as radio technology such as a global system for mobile communications (GSM)/general packet radio service (GPRS)/enhanced data rates for GSM evolution (EDGE). The OFDMA may be implemented as radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Evolved UTRA (E-UTRA), or the like. The UTRA is a part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using the E-UTRA and LTE-Advanced (A)/LTE-A pro is an evolved version of the 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of the 3GPP LTE/LTE-A/LTE-A pro.

For clarity of description, the technical spirit of the present disclosure is described based on the 3GPP communication system (e.g., LTE-A or NR), but the technical spirit of the present disclosure are not limited thereto. LTE means technology after 3GPP TS 36.xxx Release 8. In detail, LTE technology after 3GPP TS 36.xxx Release 10 is referred to as the LTE-A and LTE technology after 3GPP TS 36.xxx Release 13 is referred to as the LTE-A pro. The 3GPP NR means technology after TS 38.xxx Release 15. The LTE/NR may be referred to as a 3GPP system. “xxx” means a detailed standard document number. The LTE/NR may be collectively referred to as the 3GPP system. Matters disclosed in a standard document opened before the present disclosure may be referred to for a background art, terms, omissions, etc., used for describing the present disclosure. For example, the following documents may be referred to.

3GPP LTE

-   -   36.211: Physical channels and modulation     -   36.212: Multiplexing and channel coding     -   36.213: Physical layer procedures     -   36.300: Overall description     -   36.331: Radio Resource Control (RRC)

3GPP NR

-   -   38.211: Physical channels and modulation     -   38.212: Multiplexing and channel coding     -   38.213: Physical layer procedures for control     -   38.214: Physical layer procedures for data     -   38.300: NR and NG-RAN Overall Description     -   36.331: Radio Resource Control (RRC) protocol specification

As more and more communication devices require larger communication capacity, there is a need for improved mobile broadband communication compared to the existing radio access technology (RAT). Further, massive machine type communications (MTCs), which provide various services anytime and anywhere by connecting many devices and objects, are one of the major issues to be considered in the next generation communication. In addition, a communication system design considering a service/UE sensitive to reliability and latency is being discussed. The introduction of next generation radio access technology considering enhanced mobile broadband communication (eMBB), massive MTC (mMTC), ultra-reliable and low latency communication (URLLC) is discussed, and in the present disclosure, the technology is called new RAT for convenience. The NR is an expression representing an example of 5G radio access technology (RAT).

Three major requirement areas of 5G include (1) an enhanced mobile broadband (eMBB) area, (2) a massive machine type communication (mMTC) area and (3) an ultra-reliable and low latency communications (URLLC) area.

Some use cases may require multiple areas for optimization, and other use case may be focused on only one key performance indicator (KPI). 5G support such various use cases in a flexible and reliable manner.

eMBB is far above basic mobile Internet access and covers media and entertainment applications in abundant bidirectional tasks, cloud or augmented reality. Data is one of key motive powers of 5G, and dedicated voice services may not be first seen in the 5G era. In 5G, it is expected that voice will be processed as an application program using a data connection simply provided by a communication system. Major causes for an increased traffic volume include an increase in the content size and an increase in the number of applications that require a high data transfer rate. Streaming service (audio and video), dialogue type video and mobile Internet connections will be used more widely as more devices are connected to the Internet. Such many application programs require connectivity always turned on in order to push real-time information and notification to a user. A cloud storage and application suddenly increases in the mobile communication platform, and this may be applied to both business and entertainment. Furthermore, cloud storage is a special use case that tows the growth of an uplink data transfer rate. 5G is also used for remote business of cloud. When a tactile interface is used, further lower end-to-end latency is required to maintain excellent user experiences. Entertainment, for example, cloud game and video streaming are other key elements which increase a need for the mobile broadband ability. Entertainment is essential in the smartphone and tablet anywhere including high mobility environments, such as a train, a vehicle and an airplane. Another use case is augmented reality and information search for entertainment. In this case, augmented reality requires very low latency and an instant amount of data.

Furthermore, one of the most expected 5G use case relates to a function capable of smoothly connecting embedded sensors in all fields, that is, mMTC. Until 2020, it is expected that potential IoT devices will reach 20.4 billions. The industry IoT is one of areas in which 5G performs major roles enabling smart city, asset tracking, smart utility, agriculture and security infra.

URLLC includes a new service which will change the industry through remote control of major infra and a link having ultra-reliability/low available latency, such as a self-driving vehicle. A level of reliability and latency is essential for smart grid control, industry automation, robot engineering, drone control and adjustment.

Multiple use cases are described more specifically.

5G may supplement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS) as means for providing a stream evaluated from gigabits per second to several hundreds of mega bits per second. Such fast speed is necessary to deliver TV with resolution of 4K or more (6K, 8K or more) in addition to virtual reality and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include immersive sports games. A specific application program may require a special network configuration. For example, in the case of VR game, in order for game companies to minimize latency, a core server may need to be integrated with the edge network server of a network operator.

An automotive is expected to be an important and new motive power in 5G, along with many use cases for the mobile communication of an automotive. For example, entertainment for a passenger requires a high capacity and a high mobility mobile broadband at the same time. The reason for this is that future users continue to expect a high-quality connection regardless of their location and speed. Another use example of the automotive field is an augmented reality dashboard. The augmented reality dashboard overlaps and displays information, identifying an object in the dark and notifying a driver of the distance and movement of the object, over a thing seen by the driver through a front window. In the future, a wireless module enables communication between automotives, information exchange between an automotive and a supported infrastructure, and information exchange between an automotive and other connected devices (e.g., devices accompanied by a pedestrian). A safety system guides alternative courses of a behavior so that a driver may drive more safely, thereby reducing a danger of an accident. A next step will be a remotely controlled or self-driven vehicle. This requires very reliable, very fast communication between different self-driven vehicles and between an automotive and infra. In the future, a self-driven vehicle may perform all driving activities, and a driver will be focused on things other than traffic, which cannot be identified by an automotive itself. Technical requirements of a self-driven vehicle require ultra-low latency and ultra-high speed reliability so that traffic safety is increased up to a level which cannot be achieved by a person.

A smart city and smart home mentioned as a smart society will be embedded as a high-density radio sensor network. The distributed network of intelligent sensors will identify the cost of a city or home and a condition for energy-efficient maintenance. A similar configuration may be performed for each home. All of a temperature sensor, a window and heating controller, a burglar alarm and home appliances are wirelessly connected. Many of such sensors are typically a low data transfer rate, low energy and a low cost. However, for example, real-time HD video may be required for a specific type of device for surveillance.

The consumption and distribution of energy including heat or gas are highly distributed and thus require automated control of a distributed sensor network. A smart grid collects information, and interconnects such sensors using digital information and a communication technology so that the sensors operate based on the information. The information may include the behaviors of a supplier and consumer, and thus the smart grid may improve the distribution of fuel, such as electricity, in an efficient, reliable, economical, production-sustainable and automated manner. The smart grid may be considered to be another sensor network having small latency.

A health part owns many application programs which reap the benefits of mobile communication. A communication system may support remote treatment providing clinical treatment at a distant place. This helps to reduce a barrier for the distance and may improve access to medical services which are not continuously used at remote farming areas. Furthermore, this is used to save life in important treatment and an emergency condition. A radio sensor network based on mobile communication may provide remote monitoring and sensors for parameters, such as the heart rate and blood pressure.

Radio and mobile communication becomes increasingly important in the industry application field. Wiring requires a high installation and maintenance cost. Accordingly, the possibility that a cable will be replaced with reconfigurable radio links is an attractive opportunity in many industrial fields. However, to achieve the possibility requires that a radio connection operates with latency, reliability and capacity similar to those of the cable and that management is simplified. Low latency and a low error probability is a new requirement for a connection to 5G.

Logistics and freight tracking is an important use case for mobile communication, which enables the tracking inventory and packages anywhere using a location-based information system. The logistics and freight tracking use case typically requires a low data speed, but a wide area and reliable location information.

In a new RAT system including NR uses an OFDM transmission scheme or a similar transmission scheme thereto. The new RAT system may follow OFDM parameters different from OFDM parameters of LTE. Alternatively, the new RAT system may follow numerology of conventional LTE/LTE-A as it is or have a larger system bandwidth (e.g., 100 MHz). Alternatively, one cell may support a plurality of numerologies. In other words, UEs that operate with different numerologies may coexist in one cell.

The numerology corresponds to one subcarrier spacing in a frequency domain. Different numerologies may be defined by scaling reference subcarrier spacing to an integer N.

DEFINITION OF TERMS

eLTE eNB: The eLTE eNB is the evolution of eNB that supports connectivity to EPC and NGC.

gNB: A node which supports the NR as well as connectivity to NGC.

New RAN: A radio access network which supports either NR or E-UTRA or interfaces with the NGC.

Network slice: A network slice is a network created by the operator customized to provide an optimized solution for a specific market scenario which demands specific requirements with end-to-end scope.

Network function: A network function is a logical node within a network infrastructure that has well-defined external interfaces and well-defined functional behavior.

NG-C: A control plane interface used on NG2 reference points between new RAN and NGC.

NG-U: A user plane interface used on NG3 references points between new RAN and NGC.

Non-standalone NR: A deployment configuration where the gNB requires an LTE eNB as an anchor for control plane connectivity to EPC, or requires an eLTE eNB as an anchor for control plane connectivity to NGC.

Non-standalone E-UTRA: A deployment configuration where the eLTE eNB requires a gNB as an anchor for control plane connectivity to NGC.

User plane gateway: A termination point of NG-U interface.

Overview of System

FIG. 1 illustrates an example of an overall structure of a NR system to which a method proposed in the present disclosure is applicable.

Referring to FIG. 1, an NG-RAN consists of gNBs that provide an NG-RA user plane (new AS sublayer/PDCP/RLC/MAC/PHY) and control plane (RRC) protocol terminations for a user equipment (UE).

The gNBs are interconnected with each other by means of an Xn interface.

The gNBs are also connected to an NGC by means of an NG interface.

More specifically, the gNBs are connected to an access and mobility management function (AMF) by means of an N2 interface and to a user plane function (UPF) by means of an N3 interface.

New Rat (NR) Numerology and Frame Structure

In the NR system, multiple numerologies may be supported. The numerologies may be defined by subcarrier spacing and a CP (Cyclic Prefix) overhead. Spacing between the plurality of subcarriers may be derived by scaling basic subcarrier spacing into an integer N (or μ). In addition, although a very low subcarrier spacing is assumed not to be used at a very high subcarrier frequency, a numerology to be used may be selected independent of a frequency band.

In addition, in the NR system, a variety of frame structures according to the multiple numerologies may be supported.

Hereinafter, an orthogonal frequency division multiplexing (OFDM) numerology and a frame structure, which may be considered in the NR system, will be described.

A plurality of OFDM numerologies supported in the NR system may be defined as in Table 1.

TABLE 1 μ Δf = 2^(μ) · 15 [kHz] Cyclic prefix 0 15 Normal 1 30 Normal 2 60 Normal, Extended 3 120 Normal 4 240 Normal

The NR supports multiple numerologies (or subcarrier spacing (SCS)) for supporting various 5G services. For example, when the SCS is 15 kHz, a wide area in traditional cellular bands is supported and when the SCS is 30 kHz/60 kHz, dense-urban, lower latency, and wider carrier bandwidth are supported, and when the SCS is more than 60 kHz, a bandwidth larger than 24.25 GHz is supported in order to overcome phase noise.

An NR frequency band is defined as frequency ranges of two types (FR1 and FR2). FR1 and FR2 may be configured as shown in Table 2 below. Further, FR2 may mean a millimeter wave (mmW).

TABLE 2 Frequency Range Corresponding frequency Subcarrier designation range Spacing FR1  410 MHz-7125 MHz 15, 30, 60 kHz FR2 24250 MHz-52600 MHz 60, 120, 240 kHz

Regarding a frame structure in the NR system, a size of various fields in the time domain is expressed as a multiple of a time unit of T_(s)=1/(Δf_(max)·N_(f)). In this case, Δf_(max)=480·10³, and N_(f)=4096. DL and UL transmission is configured as a radio frame having a section of T_(f)=(Δf_(max)N_(f)/100)·T_(s)=10 ms. The radio frame is composed of ten subframes each having a section of T_(sf)(Δf_(max)N_(f)/1000)·T_(s)=1 ms. In this case, there may be a set of UL frames and a set of DL frames.

FIG. 2 illustrates a relation between an uplink frame and a downlink frame in a wireless communication system to which a method proposed in the present disclosure is applicable.

As illustrated in FIG. 2, uplink frame number i for transmission from a user equipment (UE) shall start T_(TA)=N_(TA)T_(s) before the start of a corresponding downlink frame at the corresponding UE.

Regarding the numerology μ, slots are numbered in increasing order of n_(s) ^(μ)∈{0, . . . , N_(subframe) ^(slots,μ)−1} within a subframe and are numbered in increasing order of n_(s,f) ^(μ)∈{0, . . . , N_(frame) ^(slots,μ)−1} within a radio frame. One slot consists of consecutive OFDM symbols of N_(symb) ^(μ), and N_(symb) ^(μ) is determined depending on a numerology used and slot configuration. The start of slots n_(s) ^(μ) in a subframe is aligned in time with the start of OFDM symbols n_(s) ^(μ)N_(symb) ^(μ) in the same subframe.

Not all UEs are able to transmit and receive at the same time, and this means that not all OFDM symbols in a downlink slot or an uplink slot are available to be used.

Table 3 represents the number N_(symb) ^(slot) of OFDM symbols per slot, the number N_(slot) ^(frame,μ) of slots per radio frame, and the number N_(slot) ^(subframe,μ) of slots per subframe in a normal CP. Table 4 represents the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in an extended CP.

TABLE 3 μ N_(symb) ^(slot) N_(slot) ^(frame,μ) N_(slot) ^(subframe,μ) 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

TABLE 4 μ N_(symb) ^(slot) N_(slot) ^(frame,μ) N_(slot) ^(subframe,μ) 2 12 40 4

FIG. 3 illustrates an example of a frame structure in a NR system. FIG. 3 is merely for convenience of explanation and does not limit the scope of the present disclosure.

In Table 4, in case of μ=2, i.e., as an example in which a subcarrier spacing (SCS) is 60 kHz, one subframe (or frame) may include four slots with reference to Table 3, and one subframe={1, 2, 4} slots shown in FIG. 3, for example, the number of slot(s) that may be included in one subframe may be defined as in Table 3.

Further, a mini-slot may consist of 2, 4, or 7 symbols, or may consist of more symbols or less symbols.

In regard to physical resources in the NR system, an antenna port, a resource grid, a resource element, a resource block, a carrier part, etc. May be considered.

Hereinafter, the above physical resources that may be considered in the NR system are described in more detail.

First, in regard to an antenna port, the antenna port is defined so that a channel over which a symbol on an antenna port is conveyed may be inferred from a channel over which another symbol on the same antenna port is conveyed. When large-scale properties of a channel over which a symbol on one antenna port is conveyed may be inferred from a channel over which a symbol on another antenna port is conveyed, the two antenna ports may be regarded as being in a quasi co-located or quasi co-location (QC/QCL) relation. Here, the large-scale properties may include at least one of delay spread, Doppler spread, frequency shift, average received power, and received timing.

FIG. 4 illustrates an example of a resource grid supported in a wireless communication system to which a method proposed in the present disclosure is applicable.

Referring to FIG. 4, a resource grid consists of N_(RB) ^(μ)N_(sc) ^(RB) subcarriers on a frequency domain, each subframe consisting of 14·2μ OFDM symbols, but the present disclosure is not limited thereto.

In the NR system, a transmitted signal is described by one or more resource grids, consisting of N_(RB) ^(μ)N_(sc) ^(RB) subcarriers, and 2^(μ)N_(symb) ^((μ)) OFDM symbols, where N_(RB) ^(μ)≤N_(RB) ^(max,μ). N_(RB) ^(max,μ) denotes a maximum transmission bandwidth and may change not only between numerologies but also between uplink and downlink.

In this case, as illustrated in FIG. 5, one resource grid may be configured per numerology μ and antenna port p.

FIG. 5 illustrates examples of a resource grid per antenna port and numerology to which a method proposed in the present disclosure is applicable.

Each element of the resource grid for the numerology μ and the antenna port p is called a resource element and is uniquely identified by an index pair (k,l), where k=0, . . . , N_(RB) ^(μ)N_(sc) ^(RB)−1 is an index on a frequency domain, and l=0, . . . , 2^(μ) N_(symb) ^((μ))−1 refers to a location of a symbol in a subframe. The index pair (k,l) is used to refer to a resource element in a slot, where l=0, . . . , N_(symb) ^(μ)−1.

The resource element (k,l) for the numerology μ and the antenna port p corresponds to a complex value a_(k,l) ^((p,μ)). When there is no risk for confusion or when a specific antenna port or numerology is not specified, the indices p and μ may be dropped, and as a result, the complex value may be a_(k,l) ^((p)) or a_(k,l) .

Further, a physical resource block is defined as N_(sc) ^(RB) consecutive subcarriers in the frequency domain.

Point A serves as a common reference point of a resource block grid and may be obtained as follows.

-   -   offsetToPointA for PCell downlink represents a frequency offset         between the point A and a lowest subcarrier of a lowest resource         block that overlaps a SS/PBCH block used by the UE for initial         cell selection, and is expressed in units of resource blocks         assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier         spacing for FR2;     -   absoluteFrequencyPointA represents frequency-location of the         point A expressed as in absolute radio-frequency channel number         (ARFCN);

The common resource blocks are numbered from 0 and upwards in the frequency domain for subcarrier spacing configuration μ.

The center of subcarrier 0 of common resource block 0 for the subcarrier spacing configuration μ coincides with “point A”. A common resource block number n_(CRB) ^(μ) in the frequency domain and resource elements (k, l) for the subcarrier spacing configuration μ may be given by the following Equation 1.

$\begin{matrix} {n_{CRB}^{\mu} = \left\lfloor \frac{k}{N_{sc}^{RB}} \right\rfloor} & \left\lbrack {{Equation}\mspace{14mu} 1} \right\rbrack \end{matrix}$

Here, k may be defined relative to the point A so that k=0 corresponds to a subcarrier centered around the point A. Physical resource blocks are defined within a bandwidth part (BWP) and are numbered from 0 to N_(BWP,i) ^(size)−1, where i is No. Of the BWP. A relation between the physical resource block n_(PRB) in BWP i and the common resource block n_(CRB) may be given by the following Equation 2.

$\begin{matrix} {n_{CRB} = {n_{PRB} + N_{{BWP},i}^{start}}} & \left\lbrack {{Equation}\mspace{14mu} 2} \right\rbrack \end{matrix}$

Here, N_(BWP,i) ^(start) may be the common resource block where the BWP starts relative to the common resource block 0.

Bandwidth Part (BWP)

The NR system may support up to 400 MHz per component carrier (CC). If a UE which operates in wideband CC operates while continuously turning on RF for all CCs, UE battery consumption may increase. Alternatively, when several use cases (e.g., eMBB, URLLC, mMTC, V2X, etc.) which operate in one wideband CC are considered, different numerologies (e.g., sub-carrier spacing) may be supported for each frequency band in the corresponding CC. Alternatively, a capability for the maximum bandwidth may vary for each UE. By considering this, the BS may instruct the UE to operate only in a partial bandwidth rather than the entire bandwidth of the wideband CC and intends to define the corresponding partial bandwidth as the bandwidth part (BWP) for convenience. The BWP may consist of consecutive resource blocks (RBs) on the frequency axis and may correspond to one numerology (e.g., sub-carrier spacing, CP length, slot/mini-slot duration).

A base station may configure multiple BWPs even within one CC configured to the UE. As one example, a BWP occupying a relatively small frequency domain may be configured in a PDCCH monitoring slot, and a PDSCH indicated in PDCCH may be scheduled onto a BWP larger than this. Alternatively, when UEs are concentrated on a specific BWP, some UEs may be configured with other BWPs for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between neighboring cells, a partial spectrum of the entire bandwidth may be excluded and both BWPs may be configured even in the same slot. That is, the base station may configure at least one DL/UL BWP to the UE associated with the wideband CC and may activate at least one DL/UL BWP (by L1 signaling or MAC CE or RRC signaling) among configured DL/UL BWP(s) at a specific time, and switching may be indicated to another configured DL/UL BWP (by L1 signaling or MAC CE or RRC signaling) or a timer value may be switched to the fixed DL/UL BWP when a timer value is expired based on a timer. In this case, the activated DL/UL BWP is defined as an active DL/UL BWP. However, in a situation in which the UE is in an initial access process or before RRC connection is set up, the UE may not receive a configuration for the DL/UL BWP and in such a situation, the DL/UL BWP assumed by the UE is defined as an initial active DL/UL BWP.

Physical Channel and General Signal Transmission

FIG. 6 illustrates physical channels and general signal transmission. In a wireless communication system, the UE receives information from the eNB through Downlink (DL) and the UE transmits information from the eNB through Uplink (UL). The information which the eNB and the UE transmit and receive includes data and various control information and there are various physical channels according to a type/use of the information which the eNB and the UE transmit and receive.

When the UE is powered on or newly enters a cell, the UE performs an initial cell search operation such as synchronizing with the eNB (S601). To this end, the UE may receive a Primary Synchronization Signal (PSS) and a (Secondary Synchronization Signal (SSS) from the eNB and synchronize with the eNB and acquire information such as a cell ID or the like. Thereafter, the UE may receive a Physical Broadcast Channel (PBCH) from the eNB and acquire in-cell broadcast information. Meanwhile, the UE receives a Downlink Reference Signal (DL RS) in an initial cell search step to check a downlink channel status.

A UE that completes the initial cell search receives a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Control Channel (PDSCH) according to information loaded on the PDCCH to acquire more specific system information (S602).

Meanwhile, when there is no radio resource first accessing the eNB or for signal transmission, the UE may perform a Random Access Procedure (RACH) to the eNB (S603 to S606). To this end, the UE may transmit a specific sequence to a preamble through a Physical Random Access Channel (PRACH) (S603 and S605) and receive a response message (Random Access Response (RAR) message) for the preamble through the PDCCH and a corresponding PDSCH. In the case of a contention based RACH, a Contention Resolution Procedure may be additionally performed (S606).

The UE that performs the above procedure may then perform PDCCH/PDSCH reception (S607) and Physical Uplink Shared Channel (PUSCH)/Physical Uplink Control Channel (PUCCH) transmission (S608) as a general uplink/downlink signal transmission procedure. In particular, the UE may receive Downlink Control Information (DCI) through the PDCCH. Here, the DCI may include control information such as resource allocation information for the UE and formats may be differently applied according to a use purpose.

For example, in an NR system, DCI format 0_0 and DCI format 0_1 are used for scheduling of PUSCH in one cell, and DCI format 1_0 and DCI format 1_1 are used for scheduling PDSCH in one cell. Information included in DCI format 0_0 is CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI and transmitted. And, DCI format 0_1 is used for reserving PUSCH in one cell. Information included in DCI format 0_1 may be CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI and transmitted. DCI format 1_0 is used for scheduling PDSCH in one DL cell. Information included in DCI format 1_0 is CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI and transmitted. DCI format 1_1 is used for scheduling PDSCH in one cell. Information included in DCI format 1_1 is CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI and transmitted. DCI format 2_1 is used to inform PRB(s) and OFDM symbol(s) that the UE may assume that transmission is not intended. The following information included in DCI format 2_1 such as preemption indication 1, preemption indication 2, . . . , preemption indication N is CRC scrambled by INT-RNTI and transmitted.

Meanwhile, the control information which the UE transmits to the eNB through the uplink or the UE receives from the eNB may include a downlink/uplink ACK/NACK signal, a Channel Quality Indicator (CQI), a Precoding Matrix Index (PMI), a Rank Indicator (RI), and the like. The UE may transmit the control information such as the CQI/PMI/RI, etc., via the PUSCH and/or PUCCH.

DL and UL Transmission/Reception Operation

Downlink Transmission/Reception Operation

FIG. 7 illustrates an example of a downlink transmission and reception operation.

Referring to FIG. 7, the eNB may schedule downlink transmission such as the frequency/time resource, the transport layer, a downlink precoder, the MCS, etc., (S701). Specifically, the eNB may determine a beam for PDSCH transmission to the UE. In addition, the UE may receive Downlink Control Information (DCI) for downlink scheduling (i.e., including scheduling information of the PDSCH) on the PDCCH (S702). DCI format 1_0 or DCI format 1_1 may be used for the downlink scheduling and specifically, DCI format 1_1 may include information such as the following examples: Identifier for DCI formats, Bandwidth part indicator, Frequency domain resource assignment, Time domain resource assignment, PRB bundling size indicator, Rate matching indicator, ZP CSI-RS trigger, Antenna port(s), Transmission configuration indication (TCI), SRS request, Demodulation Reference Signal (DMRS) sequence initialization, Modulation and Coding Scheme (MCS), New data indicator, Redundancy Version), HARQ process number and Downlink assignment index.

In the case of 2-codeword transmission (e.g., maxNrofCodeWordsScheduledByDCI=2), an MCS/NI/RV field may be configured for each of TB 1 and TB 2.

In particular, according to each state/index indicated in an antenna port(s) field, the number of DMRS ports may be scheduled, and single-user (SU)/Multi-user (MU) transmission scheduling is also available. Specifically, each of a table/rule for an antenna port(s) field value based on ‘dmrs-Type’ and ‘maxLength’ may be defined. Number of DMRS CDM group without data/DMRS port(s)/Number of front-load symbols corresponding to one CW/two CW may be determined according to the antenna port(s) field value. In addition, the TCI field consists of 3 bits, and the QCL for the DMRS may be dynamically indicated by indicating a maximum of 8 TCI states according to the TCI field value. The UE may receive downlink data from the base station on the PDSCH (S703). When the UE detects a PDCCH including DCI format 1_0 or 1_1, the UE may decode the PDSCH according to an indication by the corresponding DCI.

Here, when the UE receives a PDSCH scheduled by DCI format 1_1, a DMRS configuration type may be configured by higher layer parameter “dmrs-Type” in the UE and the DMRS configuration type is used for receiving the PDSCH. Further, in the UE, the maximum number of front-loaded DMRS symbols for the PDSCH may be configured by higher layer parameter “maxLength.”

In the case of DMRS configuration type 1, when a single codeword is scheduled and an antenna port mapped to an index of {2, 9, 10, 11, or 30} is designated in the UE or when two codewords are scheduled in the UE, the UE assumes that all remaining orthogonal antenna ports are not associated with PDSCH transmission to another UE. Alternatively, in the case of DMRS configuration type 2, when a single codeword is scheduled and an antenna port mapped to an index of {2, 10, or 23} is designated in the UE or when two codewords are scheduled in the UE, the UE assumes that all remaining orthogonal antenna ports are not related to PDSCH transmission to another UE.

When the UE receives the PDSCH, a precoding granularity P′ may be assumed as a consecutive resource block in the frequency domain. Here, P′ may correspond to one value of {2, 4, and wideband}. When P′ is determined as wideband, the UE does not predict that the PDSCH is scheduled to non-contiguous PRBs and the UE may assume that the same precoding is applied to the allocated resource. On the contrary, when P′ is determined as any one of {2 and 4}, a Precoding Resource Block (PRG) is split into P′ consecutive PRBs. The number of actually consecutive PRBs in each PRG may be one or more. The UE may assume that the same precoding is applied to consecutive downlink PRBs in the PRG.

In order to determine a modulation order in the PDSCH, a target code rate, and a transport block size, the UE may first read a 5-bit MCD field in the DCI and determine the modulation order and the target code rate. In addition, the UE may read a redundancy version field in the DCI and determine a redundancy version. In addition, the UE may determine the transport block size by using the number of layers before rate matching and the total number of allocated PRBs.

A transport block may be made up of one or more code block groups (CBG), and one CBG may be made up of one or more code blocks (CB). Also, in an NR system, data transmission and reception may be performed for each CB/CBG as well as for each transport block. Accordingly, ACK/NACK transmission and retransmission per CB/CBG also may be possible. The UE may receive information on CB/CBG from the base station through a DCI (e.g., DCI format 0_1 and DCI format 1_1). Also, the UE may receive information on a data transmission unit (e.g., TB/CB/CBG) from the base station.

Meanwhile, mapping a codeword, a layer, and an antenna port for the PDSCH is as follows. Modulated symbols d^((q))(0), . . . , d^((q))(M_(symb) ^((q))−1) of a complex value for a codeword (CW) q are mapped to layers x(i)=[x⁽⁰⁾(i) . . . x^((v-1))(i)]^(T), i=0, 1, . . . , M_(symb) ^(layer)−1. and the layers x(i) are mapped to antenna ports according to Equation 3. Here, v represents the number of layers, and M_(symb) ^(layer) represents the number of modulated symbols per layer.

$\begin{matrix} {\begin{bmatrix} {y^{(p_{0})}(i)} \\ \vdots \\ {y^{(p_{\upsilon - 1})}(i)} \end{bmatrix} = \begin{bmatrix} {x^{(0)}(i)} \\ \vdots \\ {x^{({\upsilon - 1})}(i)} \end{bmatrix}} & \left\lbrack {{Equation}\mspace{14mu} 3} \right\rbrack \end{matrix}$ where,

A set {p₀, . . . , p_(v-1)} of the antenna ports may be determined according to a procedure of [4, TS 38.212]. That is, the antenna ports may be sequentially mapped to the layers in the order of DMRS ports indicated to the UE through DMRS table.

UL Transmission/Reception Operation

FIG. 8 illustrates an example of an uplink transmission and reception operation.

Referring to the FIG. 8, the eNB may schedule uplink transmission such as the frequency/time resource, the transport layer, an uplink precoder, the MCS, etc., (S801). In particular, the eNB may determine a beam for PUSCH transmission of the UE through the beam management operations described above. And, the UE may receive, from the eNB, DCI for uplink scheduling (i.e., including scheduling information of the PUSCH) on the PDCCH (S802). DCI format 0_0 or 0_1 may be used for the uplink scheduling and in particular, DCI format 0_1 may include information such as the following examples: Identifier for DCI formats, UL/Supplementary uplink (SUL) indicator, Bandwidth part indicator, Frequency domain resource assignment, Time domain resource assignment, Frequency hopping flag, Modulation and coding scheme (MCS), SRS resource indicator (SRI), Precoding information and number of layers, Antenna port(s), SRS request, DMRS sequence initialization, and Uplink Shared Channel (UL-SCH) indicator.

In particular, configured SRS resources in an SRS resource set associated with higher layer parameter “usage” may be indicated by an SRS resource indicator field. Further, “spatialRelationInfo” may be configured for each SRS resource and a value of “spatialRelationInfo” may be one of {CRI, SSB, and SRI}.

In addition, the UE may transmit the uplink data to the eNB on the PUSCH (S803). When the UE detects a PDCCH including DCI format 0_0 or 0_1, the UE may transmit the corresponding PUSCH according to the indication by the corresponding DCI. two schemes (Codebook based transmission scheme and non-codebook based transmission scheme) are supported for PUSCH transmission.

In the case of the codebook based transmission, when higher layer parameter txConfig” is set to “codebook”, the UE is configured to the codebook based transmission. On the contrary, when higher layer parameter txConfig” is set to “nonCodebook”, the UE is configured to the non-codebook based transmission. When higher layer parameter “txConfig” is not configured, the UE does not predict that the PUSCH is scheduled by DCI format 0_1. When the PUSCH is scheduled by DCI format 0_0, the PUSCH transmission is based on a single antenna port. In the case of the codebook based transmission, the PUSCH may be scheduled by DCI format 0_0, DCI format 0_1, or semi-statically. When the PUSCH is scheduled by DCI format 0_1, the UE determines a PUSCH transmission precoder based on the SRI, the Transmit Precoding Matrix Indicator (TPMI), and the transmission rank from the DCI as given by the SRS resource indicator and the Precoding information and number of layers field. The TPMI is used for indicating a precoder to be applied over the antenna port and when multiple SRS resources are configured, the TPMI corresponds to the SRS resource selected by the SRI. Alternatively, when the single SRS resource is configured, the TPMI is used for indicating the precoder to be applied over the antenna port and corresponds to the corresponding single SRS resource. A transmission precoder is selected from an uplink codebook having the same antenna port number as higher layer parameter “nrofSRS-Ports”. When the UE is set to higher layer parameter “txConfig” set to “codebook”, at least one SRS resource is configured in the UE. An SRI indicated in slot n is associated with most recent transmission of the SRS resource identified by the SRI and here, the SRS resource precedes PDCCH (i.e., slot n) carrying the SRI.

In the case of the non-codebook based transmission, the PUSCH may be scheduled by DCI format 0_0, DCI format 0_1, or semi-statically. When multiple SRS resources are configured, the UE may determine the PUSCH precoder and the transmission rank based on a wideband SRI and here, the SRI is given by the SRS resource indicator in the DCI or given by higher layer parameter “srs-ResourceIndicator”. The UE may use one or multiple SRS resources for SRS transmission and here, the number of SRS resources may be configured for simultaneous transmission in the same RB based on the UE capability. Only one SRS port is configured for each SRS resource. Only one SRS resource may be configured to higher layer parameter “usage” set to “nonCodebook”. The maximum number of SRS resources which may be configured for non-codebook based uplink transmission is 4. The SRI indicated in slot n is associated with most recent transmission of the SRS resource identified by the SRI and here, the SRS transmission precedes PDCCH (i.e., slot n) carrying the SRI.

Demodulation Reference Signal (DMRS)

A DMRS related operation for receiving the PDSCH will be described.

When the PDSCH scheduled by DCI format 1_0 or when the PDSCH is received before configuring a random dedicated higher layer among dmrs-AdditionalPosition, maxLength, and dmrs-Type parameters, the UE assumes that there is no PDSCH in a random symbol carrying a DM-RS except for a PDSCH having allocation duration of two symbols having PDSCH mapping type B, a single symbol front-loaded DM-RS of configuration type 1 is transmitted on the DM-RS port 100, and all remaining orthogonal antenna ports are not related to transmission of the PDSCH to the other UE.

Additionally, for a PDSCH having mapping type A, the UE assumes that dmrs−AdditionalPosition=‘pos2’ and there are up to two additional single-symbol DMRSs in a slot according to PDSCH duration indicated by the DCI. With respect to a PDSCH having allocation duration of 7 symbols for a normal CP having mapping type B or 6 symbols for an extended CP, when the front-loaded DMRS symbol is present in each of 1st and 2nd symbols of the PDSCH allocation duration, the assumes that one additional single symbol DMRS is present in a 5th or 6th symbol. Otherwise, the UE assumes that there is no additional DMRS symbol. In addition, for a PDSCH having allocation duration of 4 symbols having mapping type B, the UE assumes that an additional DM-RS is present no longer and for a PDSCH having allocation duration of 2 symbols having mapping type B, the UE assumes that the additional DM-RS is not present and the UE assumes that the PDSCH is present in a symbol for carrying the DM-RS.

FIG. 9 is a flowchart illustrating an example of a DL DMRS procedure.

-   -   The BS transmits, to the UE, DMRS configuration information         (S910).

The DMRS configuration information may refer to DMRS-DownlinkConfig IE. The DMRS-DownlinkConfig IE may include parameter dmrs-Type, parameter dmrs-AdditionalPosition, parameter maxLength, parameter phaseTrackingRS, etc.

The dmrs-Type parameter is a parameter for selecting DMRS configuration type to be used for DL. In the NR, the DMRS may be divided into two configuration types of (1) DMRS configuration type 1 and (2) DMRS configuration type 2. DMRS configuration type 1 is a type having a higher RS density in the frequency domain and DMRS configuration type 2 is a type having more DMRS antenna ports.

The parameter dmrs-AdditionalPosition is a parameter representing a position of additional DMRS in DL. When the corresponding parameter is not present, the UE applies a value of pos2. In respect to the DMRS, a first position of the front-loaded DRMS may be determined according to a PDSCH mapping type (type A or type B) and additional DRMS may be configured in order to support a high speed UE. The front-loaded DMRS occupies 1 or 2 continuous OFDM symbols and is indicated by RRC signaling and downlink control information (DCI).

The parameter maxLength is a parameter representing the maximum number of OFDM symbols for the DL front-loaded DMRS. The parameter phaseTrackingRS is parameter for configuring DL PTRS. When the corresponding parameter is not preset or is cancelled, the UE assumes that there is no DL PATRS.

-   -   The BS generates a sequence used for the DMRS (S920).

The sequence for the DMRS is generated according to Equation 4 below.

$\begin{matrix} {{r(n)} = {{\frac{1}{\sqrt{2}}\left( {1 - {2 \cdot {c\left( {2n} \right)}}} \right)} + {j\frac{1}{\sqrt{2}}\left( {1 - {2 \cdot {c\left( {{2n} + 1} \right)}}} \right)}}} & \left\lbrack {{Equation}\mspace{14mu} 4} \right\rbrack \end{matrix}$

The pseudo-random sequence c(i) is defined in 3gpp TS 38.211 5.2.1. That is, c(i) may be a length 31 gold sequence using 2 m-sequences. A pseudo-random sequence generator is initialized by Equation 5 below.

$\begin{matrix} {c_{init} = \left( {{2^{17}\left( {{N_{symb}^{slot}n_{s,f}^{\mu}} + l + 1} \right)\left( {{2N_{ID}^{n_{SCID}}} + 1} \right)} + {\left. \quad{{2N_{ID}^{n_{SCID}}} + n_{SCID}} \right){mod}\; 2^{31}}} \right.} & \left\lbrack {{Equation}\mspace{14mu} 5} \right\rbrack \end{matrix}$

Here, l represents a number of the OFDM symbol in the slot and n_(s,f) ^(μ) represents a slot number in the frame.

In addition, if N_(ID) ⁰,N_(ID) ¹∈{0, 1, . . . , 65535} is provided and the PDSCH is scheduled by PDCCH using DCI format 1_1 having CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI, N_(ID) ⁰,N_(ID) ¹∈{0, 1, . . . , 65535} is given by each of higher-layer parameter scramblingID0 and scramblingID1 in DMRS-DownlinkConfig IE.

-   -   If N_(ID) ⁰∈{0, 1, . . . , 65535} is provided and the PDSCH is         scheduled by PDCCH using DCI format 1_0 having CRC scrambled by         C-RNTI, MCS-C-RNTI, or CS-RNTI, N_(ID) ⁰∈{0, 1, . . . , 65535}         is given by higher-layer parameter scramblingID0 in         DMRS-DownlinkConfig IE.     -   N_(ID) ^(n) ^(SCID) +N_(ID) ^(cell), otherwise, when DCI format         1_1 is used, quantity n_(SCID)∈{0, 1} is given by a DMRS         sequence initialization field in the DCI related to PDSCH         transmission.     -   The BS maps the generated sequence to a resource element (S930).         Here, the resource element may include at least one of a time, a         frequency, an antenna port, or a code.

A location l0 of a first DMRS symbol and a reference point I may be determined according to a mapping type. In Mapping type A, the DMRS location may be fixed to a third location (pos 2) or a fourth location (pos 3), and a start symbol of the PDSCH may be 0 to 3. A PDSCH length may be 3 to 14 in the case of a normal CP and 3 to 12 in the case of an extended CP. A DMRS symbol may start in a second or third symbol regardless of a start and a length of the PDSCH and this means that a case where a start symbol of the PDSCH is larger than 3 may not be applied. Mapping type A is used for slot based scheduling. Meanwhile, in Mapping type B, the DMRS location is fixed to a first symbol of the allocated PDSCH. The start symbol of the PDSCH may be 0 to 12 in the case of the normal CP and 0 to 10 in the case of the extended CP. The PDSCH length may be 2, 4, or 7 symbols in the case of the normal CP and 2, 4, or 6 symbols in the case of the extended CP. The DMRS symbol may start in the first PDSCH symbol regardless of the PDSCH start. Mapping type B may be used for mini-slot based scheduling.

-   -   The BS transmits, to the UE, the DMRS on the resource element         (S940). The UE receives the PDSCH by using the received DMRS.

UE DM-RS Transmission Procedure

A DMRS related operation for receiving the PUSCH will be described. As described above, UL means signal transmission (or communication) from the UE to the BS. A UL DMRS related operation is similar to the DL DMRS related operation described above, and names of the parameters related to DL may be replaced with the names of parameters related to UL.

That is, DMRS-DownlinkConfig IE may be replaced with DMRS-UplinkConfig IE, PDSCH mapping type may be replaced with PUSCH mapping type, and the PDSCH may be replaced with the PUSCH. In addition, in the DL DMRS related operation, the BS may be replaced with the UE and the UE may be replaced with the BS. Sequence generation for the UL DMRS may be defined differently according to whether transform precoding is enabled.

Hereinafter, the UE DM-RS transmission procedure will be described in more detail.

When the transmitted PUSCH is not scheduled by DCI format 0_1 having CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI and does not correspond to a configured grant, the UE uses a single symbol front-loaded DMRS of configuration type 1 in DMRS port 0 and does not use the remaining REs even in any PUSCH transmission other than a PUSCH having allocation duration of two OFDM symbols or less having disabled transform precoding. Additional DM-RS may be transmitted according to a scheduling type and PUSCH duration by considering whether frequency hopping is enabled.

When the frequency hopping is disabled, the UE assumes that dmrs-AdditionalPosition is equal to ‘pos2’, and up to 1 additional DM-RSs may be transmitted according to the PUSCH duration. When the frequency hopping is enabled, the UE assumes that dmrs-AdditionalPosition is equal to ‘pos1’, and up to 1 additional DM-RS may be transmitted according to the PUSCH duration.

When the transmitted PUSCH is scheduled by activation DCI format 0_0 having CRC scrambled by CS-RNTI, the UE uses a single symbol front-loaded DMRS of a configuration type provided by a higher layer parameter dmrs-Type of configuredGrantConfig on DMRS port 0 and does not use remaining REs which are not used for the DMRS in the symbols even for any PUSCH transmission other than the PUSCH having the allocation duration of two OFDM symbols or less having the disabled transform precoding, and an additional DMRS having dmrs-AdditionalPosition from configuredGrantConfig may be transmitted based on a scheduling type and PUSCH duration by considering whether the frequency hopping is enabled.

When the transmitted PUSCH is scheduled by DCI format 0_1 having CRC scrambled by C-RNTI, CS-RNTI, or MCS-RNTI or corresponds to the configured grant,

-   -   the UE may be configured as the higher layer parameter drms-Type         in DMRS-UplinkConfig and the configured DM-RS configuration type         is used for transmitting the PDSCH.     -   The UE may be configured as a maximum number of front-loaded         DMRS symbols for the PUSCH by the higher layer parameter         maxLength given by DMRS-UplinkConfig.

When the UE transmitting the PUSCH is configured as higher layer parameter phaseTrackingRS in DMRS-UplinkConfig, the UE may assume that the configurations do not simultaneously occur for the transmitted PUSCH.

-   -   Each random DM-RS port of 4-7 or 6-11 is scheduled by the UE for         DM-RS configuration type 1 and type 2 and the PT-RS is         transmitted from the UE.

For the PUSCH scheduled by DCI format 0_1, by activation DCI format 0_1 having the CRC scrambled by the CS-RNTI or by configured grant type 1 configuration, the UE assumes that a DM-RS CDM group is not used for data transmission.

Quasi-Co Location (QCL).

The antenna port is defined so that a channel over which a symbol on an antenna port is conveyed may be inferred from a channel over which another symbol on the same antenna port is conveyed. When properties of a channel over which a symbol on one antenna port is conveyed may be inferred from a channel over which a symbol on another antenna port is conveyed, the two antenna ports may be considered as being in a quasi co-located or quasi co-location (QC/QCL) relationship.

The channel properties include one or more of delay spread, Doppler spread, frequency/Doppler shift, average received power, received timing/average delay, and spatial RX parameter. The spatial Rx parameter means a spatial (reception) channel property parameter such as an angle of arrival.

The UE may be configured with a list of up to M TCI-State configurations within the higher layer parameter PDSCH-Config to decode PDSCH according to a detected PDCCH with DCI intended for the corresponding UE and a given serving cell, where M depends on UE capability (e.g. maxNumberActiveTCI-PerBWP).

Each TCI-State contains parameters for configuring a quasi co-location relationship between one or two DL reference signals and the DM-RS ports of the PDSCH.

The quasi co-location relationship is configured by the higher layer parameter qcl-Type1 for the first DL RS and qcl-Type2 for the second DL RS (if configured). For the case of two DL RSs, the QCL types are not be the same, regardless of whether the references are to the same DL RS or different DL RSs.

The quasi co-location types corresponding to each DL RS are given by the higher layer parameter qcl-Type of QCL-Info and may take one of the following values:

-   -   ‘QCL-TypeA’: {Doppler shift, Doppler spread, average delay,         delay spread}     -   ‘QCL-TypeB’: {Doppler shift, Doppler spread}     -   ‘QCL-TypeC’: {Doppler shift, average delay}     -   ‘QCL-TypeD’: {Spatial Rx parameter}

For example, if a target antenna port is a specific NZP CSI-RS, the corresponding NZP CSI-RS antenna ports may be indicated/configured to be QCLed with a specific TRS in terms of QCL-TypeA and with a specific SSB in terms of QCL-TypeD. The UE receiving the indication/configuration may receive the corresponding NZP CSI-RS using the Doppler or delay value measured in the QCL-TypeA TRS and apply the Rx beam used for QCL-TypeD SSB reception to the reception of the corresponding NZP CSI-RS reception.

The UE may receive an activation command by MAC CE signaling used to map up to eight TCI states to the codepoint of the DCI field ‘Transmission Configuration Indication’.

The standard content related to the above-described QCL may be the same Table 5 below (e.g. see 3gpp TS 38.214. section 5.1.5.).

TABLE 5 When the HARQ-ACK corresponding to the PDSCH carrying the activation command is transmitted in slot n, the indicated mapping between TCI states and codepoints of the DCI field ‘Transmission Configuration Indication’ should be applied starting from slot n + 3N_(slot) ^(subframe,μ) + 1. After a UE receives an initial higher layer configuration of TCI states and before reception of the activation command, the UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the SS/PBCH block determined in the initial access procedure with respect to ‘QCL-TypeA’, and when applicable, also with respect to‘QCL-TypeD’. If a UE is configured with the higher layer parameter tci-PresentInDCI that is set as ‘enabled’ for the CORESET scheduling the PDSCH, the UE assumes that the TCI field is present in the DCI format 1_1 of the PDCCH transmitted on the CORESET. If tci-PresentInDCI is not configured for the CORESET scheduling the PDSCH or the PDSCH is scheduled by a DCI format 1_0, and the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than a threshold timeDurationForQCL, where the threshold is based on reported UE capability [13, TS 38.306], for determining PDSCH antenna port quasi co-location, the UE assumes that the TCI state or the QCL assumption for the PDSCH is identical to the TCI state or QCL assumption whichever is applied for the CORESET used for the PDCCH transmission. If the tci-PresentInDCI is set as ‘enabled’, the TCI field in DCI in the scheduling component carrier points to the activated TCI states in the scheduled component carrier or DL BWP and when the PDSCH is scheduled by DCI format 1_1, the UE shall use the TCI-State according to the value of the ‘Transmission Configuration Indication’ field in the detected PDCCH with DCI for determining PDSCH antenna port quasi co-location. The UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the RS(s) in the TCI state with respect to the QCL type parameter(s) given by the indicated TCI state if the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than a threshold timeDurationForQCL, where the threshold is based on reported UE capability [13, TS 38.306]. When the UE is configured with a single slot PDSCH, the indicated TCI state should be based on the activated TCI states in the slot with the scheduled PDSCH. When the UE is configured with a multi-slot PDSCH, the indicated TCI state should be based on the activated TCI states in the first slot with the scheduled PDSCH, and UE shall expect the activated TCI states are the same across the slots with the scheduled PDSCH. When the UE is configured with CORESET associated with a search space set for cross-carrier scheduling, the UE expects tci-PresentInDci is set as ‘enabled’ for the CORESET, and if one or more of the TCI states configured for the serving cell scheduled by the search space set contains ‘QCL-TypeD’, the UE expects the time offset between the reception of the detected PDCCH in the search space set and the corresponding PDSCH is larger than or equal to the threshold timeDurationForQCL. For both the cases when tci-PresentInDCI is set to ‘enabled’ and tci-PresentInDCI is not configured in RRC connected mode, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, the UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) used for PDCCH quasi co-location indication of the CORESET associated with a monitored search space with the lowest CORESET-ID in the latest slot in which one or more CORESETs within the active BWP of the serving cell are monitored by the UE. In this case, if the ‘QCL-TypeD’ of the PDSCH DM-RS is different from that of the PDCCH DM-RS with which they overlap in at least one symbol, the UE is expected to prioritize the reception of PDCCH associated with that CORESET. This also applies to the intra-band CA case (when PDSCH and the CORESET are in different component carriers). If none of configured TCI states contains ‘QCL-TypeD’, the UE shall obtain the other QCL assumptions from the indicated TCI states for its scheduled PDSCH irrespective of the time offset between the reception of the DL DCI and the corresponding PDSCH.

In relation to the beam indication, the UE may be RRC-configured with a list for up to M candidate Transmission Configuration Indication (TCI) states for the purpose of at least Quasi Co-location (QCL) indication, where M may be 64.

Each TCI state may be configured in one RS set. IDs of each DL RS for the purpose of spatial QCL (QCL Type D) at least in the RS set may refer to one of DL RS types such as SSB, P-CSI RS, SP-CSI RS, and A-CSI RS. Initialization/update for the ID of DL RS(s) in the RS set that are used at least for the purpose of spatial QCL may be performed at least by explicit signaling.

The TCI-State IE associates one or two DL reference signals (RS) with a corresponding quasi co-location (QCL) type. The TCI-State IE may include parameters such as bwp-Id/reference signal/QCL type.

A bwp-Id parameter indicates DL BWP where RS is positioned, a cell parameter indicates a carrier where RS is positioned, a reference signal parameter indicates a reference antenna port(s) that is a source of quasi co-location for a corresponding target antenna port(s), or a reference signal including it. The target antenna port(s) may be CSI-RS, PDCCH DMRS, or PDSCH DMRS. For example, a corresponding TCI state ID may be indicated to NZP CSI-RS resource configuration information to indicate QCL reference RS information for NZP CSI-RS. As another example, a TCI state ID may be indicated in each CORESET configuration to indicate QCL reference information for the PDCCH DMRS antenna port(s). As another example, a TCI state ID may be indicated through DCI to indicate QCL reference information for the PDSCH DMRS antenna port(s).

The descriptions (e.g., 3GPP system, frame structure, DL and UL transmission and reception, etc.) given above may be applied/used in combination with methods and/or embodiments proposed in the present disclosure or may be supplemented to clarify technical features of the methods proposed in the present disclosure. In the present disclosure, the presence of a slash “/” may indicate that all or only some of words or phrases separated by / are included.

Multiple Transmission and Reception Point (TRP)-Related Operation

The coordinated multi point (CoMP) technique is a scheme in a plurality of base stations exchange (e.g., use X2 interface) or utilize channel information (e.g., RI/CQI/PM/LI, etc.) fed back from the user equipment (UE) to perform cooperative transmission with the UE, thereby effectively controlling interference. According to the scheme used, the cooperative transmission may be divided into joint transmission (JT), coordinated scheduling (CS), coordinated beamforming (CB), dynamic point selection (DPS), dynamic point blacking (DPB), and the like.

Non-coherent joint transmission (NCJT) may refer to cooperative transmission that does not consider interference (that is, with no interference). For example, the NCJT may be a scheme in which a base station(s) transmits data to one UE through multiple TRPs by using the same time resource and frequency resource. In this scheme, the multiple TRPs of the base station(s) may be configured to transmit data to UE through different layers by using different demodulation reference signal (DMRS) ports. In other words, the NCJT may correspond to a transmission scheme in which transmission of a MIMO layer(s) from two or more TRPs is performed without adaptive precoding between the TRPs.

The NCJT may be categorized into fully overlapped NCJT, in which time and frequency resources used for transmission by each base station (or TRP) are fully overlapped, and partially overlapped NCJT, in which time and frequency resources used for transmission by each base station (or TRP) are partially overlapped. This is only for convenience of explanation in the present disclosure, and it is needless to say that, in the embodiments and methods to be described below, the above-mentioned terms can be replaced with other terms with the same technical meanings. For example, in the case of partially overlapped NCJT, both data of a first base station (e.g., TRP 1) and data of a second base station (e.g., TRP 2) may be transmitted in some of the time resources and/or frequency resources, and data of only one of the first and second base stations may be transmitted in the remaining time resources and/or frequency resources.

TRP transmits data scheduling information to an NCJT receiving UE as DCI (Downlink Control Information). From the perspective of downlink control information (DCI) transmission, M-TRP (multiple TRP) transmission may be divided into i) M-DCI (multiple DCI) based M-TRP transmission in which each TRP transmits a different DCI and ii) S-DCI (single DCI) based M-TRP transmission in which one TRP transmits DCI.

Firstly, the single DCI based MTRP scheme will be described. In the single DCI based MTRP scheme in which a representative TRP transmits scheduling information for data transmitted by itself and data transmitted by another TRP through one DCI, MTRPs cooperatively transmit one common PDSCH and each TRP participating in the cooperative transmission spatially divides the corresponding PDSCH into different layers (i.e., different DMRS ports). In other words, MTRPs transmit one PDSCH but each TRP transmits only some of multiple layers of the PDSCH. For example, when 4-layer data is transmitted, TRP 1 transmits 2 layers, and TRP 2 transmits the remaining 2 layers to the UE.

In this case, scheduling information for the PDSCH is indicated to the UE through one DCI, and the corresponding DCI indicates which DMRS port uses information of which QCL RS and QCL type (which is different from conventionally indicating the QCL RS and TYPE that are commonly applied to all DMRS ports indicated by the DCI). That is, M TCI states (M=2 for 2 TRP cooperative transmission) are indicated through the TCI field in the DCI, and the QCL RS and type are identified by using M TCI states which are different for M DMRS port groups. Also, DMRS port information may be indicated by using a new DMRS table.

As an example, in the case of the S-DCI, since all scheduling information for data transmitted by M TRPs should be delivered through one DCI, the S-DCI may be used in an ideal backhaul (BH) environment in which two TRPs may be dynamically coordinated with each other.

Secondly, the multiple DCI based MTRP method will be described. MTRPs transmit different DCIs and PDSCHs, respectively (the UE receives N DCIs and N PDSCHs from N TRPs), and the corresponding PDSCHs are transmitted by (partially or wholly) overlapping on different time resources. The corresponding PDSCHs are transmitted through different scrambling IDs, and the corresponding DCIs may be transmitted through Coresets belonging to different Coreset groups (A coreset group may be identified as an index defined in the coreset configuration of each Coreset. For example, if Coresets 1 and 2 are set to index=0 and Coresets 3 and 4 are set to index=1, Coresets 1 and 2 belong to Coreset group 0 and Coresets 3 and 4 belong to Coreset group 1. If no index is defined for a coreset, this may be interpreted as index=0). If multiple scrambling IDs are set in one serving cell or two or more coreset groups are set, the UE may know that data is received by multiple DCI-based MTRP operation.

For example, the single DCI based MTRP scheme or the multiple DCI based MTRP scheme may be indicated to the UE via separate signaling. As an example, when a plurality of CRS patterns are indicated to the UE for MTRP operation for one serving cell, PDSCH rate matching for CRS may be different depending on this MTRP operation is a single DCI based MTRP operation or a multiple DCI based MTRP operation.

The base station described in this disclosure may be a generic term for an object that transmits/receives data to and from UE. For example, the base station described herein may be a concept including one or more transmission points (TPs), one or more transmission and reception points (TRPs), and the like. For example, multiple TPs and/or multiple TRPs described herein may be included in one base station or included in multiple base stations. In addition, the TP and/or TRP may include a panel of a base station, a transmission and reception unit, and the like.

In addition, the TRP described in this disclosure means an antenna array having one or more antenna elements available in a network located at a specific geographical location in a specific area. Although this disclosure is described with respect to “TRP” for convenience of explanation, the TRP may be replaced with a base station, a transmission point (TP), a cell (e.g., a macro cell/small cell/pico cell, etc.), an antenna array, or a panel and understood and applied as such.

In addition, the CORESET group ID described in this disclosure may refer to an index/identification information (e.g., ID)/indicator, etc. for distinguishing a CORESET configured for/associated with each TRP/panel (or for each TRP/panel). In addition, the CORESET group may be a group/union of CORESETs which is distinguished by the index/identification information (e.g., ID) for distinguishing the CORESET and the CORESET group ID. For example, the CORESET group ID may be specific index information defined in the CORESET configuration. For example, the CORESET group may be configured/indicated/defined by an index defined in the CORESET configuration for each CORESET. The CORESET group ID may be configured/indicated via higher layer signaling (e.g., RRC signaling)/L2 signaling (e.g., MAC-CE)/L1 signaling (e.g., DCI).

For example, ControlResourceSet information element (IE) that is a higher layer parameter is used to configure a time/frequency control resource set (CORESET). For example, the control resource set may be related to detection and reception of downlink control information. Examples of the ControlResourceSet IE may include CORESET related ID (e.g., controlResourceSetID), an index of a CORESET pool for CORESET (e.g., CORESETPoolIndex), time/frequency resource configuration of CORESET, and TCI information related to CORESET. For example, the index of the CORESET pool (e.g., CORESETPoolIndex) may be set to 0 or 1.

For example, it may be indicated/configured so that PDCCH detection for each TRP/panel is performed on a per CORESET group basis. And/or, it may be indicated/configured so that uplink control information (e.g. CSI, HARQ-A/N, SR) and/or uplink physical channel resources (e.g. PUCCH/PRACH/SRS resources) for each TRP/panel are divided on a per CORESET group basis and managed/controlled. And/or, HARQ A/N (process/retransmission) for PDSCH/PUSCH, etc. scheduled for each TRP/panel may be managed on a per CORESET group basis.

Further, the UE may recognize PUSCH (or PUCCH) scheduled by DCI received by different CORESETs (or CORESETs which belong to different CORESET groups) as PUSCH (or PUCCH) transmitted to different TRPs or PUSCH (or PUCCH) of different TRPs. Further, a scheme for UL transmission (e.g., PUSCH/PUCCH) transmitted to different TRPs may be applied equally even to UL transmission (e.g., PUSCH/PUCCH) transmitted to different panels which belong to the same TRP.

M-TRP Transmission Scheme

M-TRP transmission by which multiple (e.g., M) TRPs transmit data to one user equipment (UE) may be divided into two main types of transmission: eMBB M-TRP transmission (or M-TRP eMMB) which is a scheme for increasing a transmission rate and URLLC M-TRP transmission (or M-TRP URLLC) which is a scheme for increasing a reception success rate and reducing latency.

URLLC M-TRP may mean that M-TRPs transmit the same TB (Transport Block) using different resources (e.g., layers/time resources/frequency resources, etc.). A number of TCI state(s) may be indicated by DCI to a UE configured with the URLLC M-TRP transmission scheme, and data received using the QCL reference signal (RS) of each TCI state may be assumed to be the same TB. On the other hand, eMBB M-TRP may mean that M-TRPs transmit different TBs using different resources (e.g., layers/time resources/frequency resources, etc.). A number of TCI state(s) may be indicated by DCI to a UE configured with the eMBB M-TRP transmission scheme, and data received using the QCL RS of each TCI state may be assumed to be different TBs. In relation to at least eMBB M-TRP, each TCI code point within DCI may correspond to 1 or 2 TCI states. If 2 TCI states are activated within one TCI code point, each TCI state for at least DMRS type 1 may correspond to one CDM group.

For example, the UE may decide/determine whether the corresponding M-TRP transmission is URLLC transmission or eMBB transmission since it uses the RNTI configured for MTRP-URLLC and the RNTI configured for MTRP-eMBB, separately. That is, if the CRC masking of the DCI received by the UE is performed using the RNTI configured for the MTRP-URLLC purpose, this may correspond to URLLC transmission, and if the CRC masking of the DCI is performed using the RNTI configured for the MTRP-eMBB purpose, this may correspond to eMBB transmission.

Table 6 shows various schemes that can be considered for URLLC M-TRP transmission. Referring to Table 6, there exist various schemes such as SDM/FDM/TDM.

TABLE 6 To facilitate further down-selection for one or more schemes in RANI #96bis, schemes for multi-TRP based URLLC, scheduled by single DCI at least, are clarified as following: Scheme 1 (SDM): n (n <= N_(s)) TCI states within the single slot, with overlapped time and frequency resource allocation Scheme 1a: Each transmission occasion is a layer or a set of layers of the same TB, with each layer or layer set is associated with one TCI and one set of DMRS port(s). Single codeword with one RV is used across all spatial layers or layer sets. From the UE perspective, different coded bits are mapped to different layers or layer sets with the same mapping rule as in Rel-15. Scheme 1b: Each transmission occasion is a layer or a set of layers of the same TB, with each layer or layer set is associated with one TCI and one set of DMRS port(s). Single codeword with one RV is used for each spatial layer or layer set. The RVs corresponding to each spatial layer or layer set can be the same or different. Scheme 1c: One transmission occasion is one layer of the same TB with one DMRS port associated with multiple TCI state indices, or one layer of the same TB with multiple DMRS ports associated with multiple TCI state indices one by one. For Scheme 1a and 1c, the same MCS is applied for all layers or layer sets. For scheme 1b, same or different MCS/modulation orders for different layers or layer sets can be discussed. Scheme 2 (FDM): n (n <= N_(t)) TCI states within the single slot, with non-overlapped frequency resource allocation Each non-overlapped frequency resource allocation is associated with one TCI state. Same single/multiple DMRS port(s) are associated with all non-overlapped frequency resource allocations. Scheme 2a: Single codeword with one RV is used across full resource allocation. From UE perspective, the common RB mapping (codeword to layer mapping) is applied across full resource allocation. Scheme 2b: Single codeword with one RV is used for each non-overlapped frequency resource allocation. The RVs corresponding to each non-overlapped frequency resource allocation can be the same or different. For scheme 2a, same MCS is applied for all non-overlapped frequency resource allocations For scheme 2b, same or different MCS/modulation orders for different non-overlapped frequency resource allocations can be discussed. Details of frequency resource allocation mechanism for FDM 2a/2b with regarding to allocation granularity, time domain allocation can be discussed. Scheme 3 (TDM): n (n <= N_(t1)) TCI states within the single slot, with non-overlapped time resource allocation Each transmission occasion of the TB has one TCI and one RV with the time granularity of mini-slot. All transmission occasion (s) within the slot use a common MCS with same single or multiple DMRS port(s). RV/TCI state can be same or different among transmission occasions. FFS channel estimation interpolation across mini-slots with the same TCI index Scheme 4 (TDM): n (n <= N_(t2)) TCI states with K (n <= K) different slots. Each transmission occasion of the TB has one TCI and one RV. All transmission occasion (s) across K slots use a common MCS with same single or multiple DMRS port(s) RV/TCI state can be same or different among transmission occasions. FFS channel estimation interpolation across slots with the same TCI index Note that M-TRP/panel based URLLC schemes shall be compared in terms of improved reliability, efficiency, and specification impact. Note: Support of number of layers per TRP may be discussed

For example, scheme3/4 of Table 6 is a scheme considered in TDM based URLLC. Specifically, scheme 4 means a scheme in which one TRP transmits the TB in one slot and has an effect of increasing a data reception probability through the same TB received from multiple TRPs in multiple slots. Unlike this, scheme 3 means a scheme in which one TRP transmits the TB through several consecutive OFDM symbols (i.e., symbol group), and may be configured in such a manner that multiple TRPs transmit the same TB through different symbol groups in one slot.

Method for Improving Reliability in Multi-TRPs

FIGS. 10A and 10B illustrate an example of a transmission/reception method for improving reliability supported by a plurality of TRPs, and the following two methods may be considered.

The example in FIG. 10A shows that a layer group transmitting the same codeword (CW)/transport block (TB) correspond to different TRPs. That is, the same CW may be transmitted via different layers/layer groups. In this case, a layer group may refer to some kind of layer set made up of one or more layers. As such, the amount of transmission resources increases as the number of layers increases, and this is advantageous in that robust channel coding with a low code rate can be used for TB. In addition, it is expected that the reliability of received signals may be improved based on diversity gain due to different channels from a plurality of TRPs.

The example in FIG. 10B shows an example in which different CWs are transmitted via layer groups corresponding to different TRPs. That is, different CWs may be transmitted through different layers/layer groups. In this case, it may be assumed that TBs corresponding to the first CW (CW #1) and the second CW (CW #2) are the same. Therefore, this can be seen as an example of repeated transmission of the same TB. In the case of FIG. 10B, the code rate corresponding to the TB may be higher than that of FIG. 9. Still, there is an advantage that a code rate can be adjusted by indicating different redundancy version (RV) values for encoding bits generated from the same TB according to a channel environment, or that a modulation order of each CW may be adjusted.

In FIG. 10A or FIG. 10B, the same TB is repeatedly transmitted via different layer groups, and each layer group is transmitted by different TRPs/panels, thereby increasing the data reception probability, which may be called spatial division multiplexing (SDM)-based URLLC M-TRP transmission. A layer(s) belonging to different layer groups are transmitted through DMRS ports belonging to different DMRS CDM groups, respectively.

In addition, although the above description regarding multiple TRPs has been given with respect to a spatial division multiplexing (SDM) scheme using different layers, it also may be extensively applied to a frequency division multiplexing (FDM) scheme based on different frequency domain resources (e.g., RB/PRB (set)), and/or a time division multiplexing (TDM) scheme based on different time domain resources (e.g., slots, symbols, and sub-symbols).

Hereinafter, in the present disclosure, methods that can be proposed in consideration of cooperative transmission (e.g., NCJT) between multiple base stations (e.g., multiple TPs/TRPs of one or more base stations) and UE will be described. Specifically, Proposal 1 proposes a method for configuring an eMBB operation or URLLC operation and a method for indicating/configuring a URLLC operation scheme. Proposal 2 proposes a method for configuring the number of repeated transmission times by considering the URLLC operation scheme. Proposal 3 proposes a method for configuring/indicating a transmission resource region in repeated transmission in the time domain. Proposal 4 proposes a method for defining/configuring a TCI state field in the DCI by considering the URLLC operation.

As described above, each TRP may be distinguished based on an index (e.g., CORESETPoolIndex) (or CORESET group ID) of a CORESET pool configured to a CORESET. Although the methods described herein are described based on one or more TP/TRPs of base station(s), the methods may be equally or similarly applied to transmissions based on one or more panels of base station(s).

<Proposal 1>

As described above, multi-TRP (hereinafter, M-TRP) based transmission may be classified into an eMBB operation (i.e., eMBB M-TRP) and a URLLC operation (i.e., URLLC M-TRP). The URLLC operation may be largely classified into operations of four schemes (e.g., schemes 1, 2, 3, and 4) as organized in Table 6. Since a resource configuration method and a mapping relationship between the TCI state and the resource should be defined differently for the eMBB operation and the URLLC operation, the BS needs to configure/indicate which operation is to be performed to the UE.

When a situation is considered in which transmission of data for URLLC is unexpectedly required due to occurrence of an urgent situation in a UE receiving data for eMBB, it may be preferred that the eMBB operation and the URLLC operation are dynamically indicated through the DCI rather than the eMBB operation and the URLLC operation are semi-statically configured through the higher layer signaling. In the present disclosure, the data for eMBB and the data for URLLC are described by assuming the multi-TRP transmission, but the method and/or the embodiment proposed in the present disclosure may be applied even to single TRP transmission. Further, a situation may be assumed in which the data for URLLC is transmitted in a transmission resource allocated to the UE based on scheduling of the BS. For example, the UE may receive the data for URLLC through the PDSCH scheduled through the DCI of the corresponding PDCCH after detecting the PDCCH in the CORESET.

Hereinafter, the method for configuring an eMBB operation or URLLC operation to the UE and the method for indicating/configuring a URLLC operation scheme proposed in the present disclosure will be described in detail.

The BS may configure, to the UE, in which scheme among multiple URLLC operations (e.g., scheme 1 to scheme 4) to perform URLLC M-TRP transmission through the higher layer signaling. For example, a higher layer parameter (e.g., RepSchemeEnabler) for indicating one of the schemes for the URLLC operation may be configured/defined. As an example, whether the corresponding scheme is an FDM based scheme (e.g., scheme 2a/2b) or a TDM based scheme (scheme 3/4) may be configured by using the higher layer parameter.

As described in Table 6, multiple schemes related to the URLLC operation are defined, and since the schemes have a similarity in terms of reliability and latency, a specific scheme may not be required to be dynamically selected. Accordingly, a specific operation (e.g., one of schemes 2a/2b, 3, and 4) among multiple URLLC operations may be semi-statically configured to the UE through the higher layer signaling, and whether the specific URLLC operation semi-statically configured is performed may be dynamically indicated through the DCI. For example, scheme 3 (i.e., TDM scheme) may be configured to the UE through the higher layer signaling, and the URLLC operation of scheme 3 may be enabled/disabled.

Since it may be assumed that operations included in scheme 1 among the URLLC operations have no difference in terms of the UE compared with the eMBB operation, it may be assumed that the operations included in scheme 1 may be excluded from a candidate of the specific operation semi-statically configured to the UE through the higher layer signaling in the above-described example, but the operations included in scheme 1 may also be included in the candidate and semi-statically configured to the UE.

A specific field in the DCI may be used for dynamically indicating whether to perform the URLLC operation.

For example, a specific bit of field ‘Antenna port(s)’ for indicating the DMRS port in DCI (e.g., DCI format 1_1) may be used for the dynamic indication. In the following description, the DMRS port indication field may mean the field ‘Antenna port(s)’. In Proposal 1 of the present disclosure, “the specific bit of the DMRS port indication field in the DCI may be used” may mean that all or some bits constituting the corresponding field or codepoints corresponding to the corresponding bits may be used for the method and/or the embodiment of Proposal 1. Further, the interpretation may also be similarly applied even to the following other proposals (e.g., Proposals 2 to 4).

Multiple TCI states may be indicated to the UE, and in this case, the UE may implicitly know that the corresponding operation is a multi-TRP transmission operation, and optimize the DMRS port indication field by newly constituting a DMRS port combination for multi-TRP transmission. In the case of optimizing the DMRS port indication field, whether the corresponding operation is the eMBB operation or the URLLC operation may be indicated through most significant bit (MSB) or least significant bit (LSB) of the DMRS port indication field, and the DMRS port combination may be constituted by optimization to each operation by using the remaining bit(s) other than the corresponding bit among the bits constituting the DMRS port indication field.

The following proposal may be together considered as a method for dynamically indicating, by the BS, to the UE, different service types such as the eMBB operation or the URLLC operation.

In the Rel-15 standard, DCI format 1_1 is used for scheduling of the PDSCH in one cell. The DCI includes the antenna port(s) field (i.e., DMRS port indication field), and the corresponding field is defined in Table 7.3.1.2.2-1/2/3/4 of TS 38.212. Hereinafter, ‘Rel-15 DMRS tables’ may mean the DMRS tables. The numbers of DRMS ports and DMRS CDM group(s) without data may be determined according to a value of the antenna port(s) field.

Meanwhile, DMRS tables having an enhanced function capable of supporting a new DMRS port combination may be introduced by considering the multi-TRP transmission, and hereinafter, ‘Rel-16 DMRS tables’ may mean the DMRS tables.

Whether the URLLC operation is performed may be dynamically indicated through Rel-16 DMRS tables. More characteristically, in a state in which the UE is configured to use the Rel-16 DMRS tables, multiple TCI states may be indicated to the UE through the DCI, and when 2 CW transmission is indicated, whether the URLLC operation is performed may be dynamically indicated through a specific codepoint(s) of the DMRS port indication field. A specific embodiment for the operation will be described below.

‘A state in which the UE is configured to use the Rel-16 DMRS tables’ may be interpreted as being configured through the higher layer signaling (e.g., RRC/MAC CE) to apply the Rel-16 DMRS tables for interpreting the DMRS port indication field in the DCI. In other words, the state may mean a case where the DMRS port indication field in the DCI is configured/indicated to be interpreted based on a newly defined DMRS table (e.g., Rel-16 DMRS tables). For example, the operation may be configured through an explicit RRC/MAC CE parameter for the purpose. Alternatively, the operation may be configured by an implicit method. As an example of the implicit method, when there is a codepoint mapped to multiple TCI states among codepoints of the TCI state field in the DCI through the MAC CE operation, the Rel-16 DMRS tables may be configured to be used.

‘A case of indicating 2-CW transmission’ may mean a case where an MCS/NDI/RV value is indicated in each TB field for transport block (TB) 1 and TB 2 in a state in which the maximum number of codewords is configured to 2 (i.e., a state in which maxNrofCodeWordsScheduledByDCI=2 is configured). Here, the TB field may mean a DCI field for indicating the MCS/NDI/RV of each TB. That is, the TB field may be a concept including an MCS field, an NDI field, and an RV field. Meanwhile, when a specific TB field is indicated as MCS=26 and RV=1, it may be interpreted that the corresponding TB is disabled, and in the proposed operation, it may be assumed that such a situation does not occur. That is, a situation may be assumed in which both TB fields do not satisfy a combination of MCS=26 and RV=1.

‘A case where whether the URLLC operation is performed is dynamically indicated through a specific codepoint(s) of the DMRS port indication field’ may mean the following case.

Table 7 as an example of a DMRS table of Rel-15 shows Table 7.3.1.2.2-2 defined in TS38.212. Referring to Table 7, when both CWs 0 and 1 are enabled (i.e., when in the case of 2 codeword transmission), the value of the DMRS port indication field may be interpreted according to a right column of two codewords, and in this case, the value of the DMRS port indication field may be indicated only for layers of 5 layers or more. In the Rel-15 DMRS table, a combination of the DMRS ports is defined only for four codepoints (e.g., values 0 to 3) for two codewords. Accordingly, the URLLC operation may be dynamically indicated by using codepoints defined as reserved up to 4-31. To this end, a new Rel-16 DMRS table may be defined based on the Rel-15 DMRS table.

TABLE 7 One Codeword: Two Codewords: Codeword 0 enabled, Codeword 0 enabled, Codeword 1 disabled Codeword 1 enabled Number Number of of DMRS Number DMRS Number CDM of CDM of group(s) front- group(s) front- without DMRS load without DMRS load Value data port(s) symbols Value data port(s) symbols  0 1 0 1 0 2 0-4 2  1 1 1 1 1 2 0, 1, 2, 3, 4, 6 2  2 1 0, 1 1 2 2 0, 1, 2, 3, 4, 5, 6 2  3 2 0 1 3 2 0, 1, 2, 3, 4, 5, 6, 7 2  4 2 1 1 4-31 reserved reserved reserved  5 2 2 1  6 2 3 1  7 2 0, 1 1  8 2 2, 3 1  9 2 0-2 1 10 2 0-3 1 11 2 0, 2 1 12 2 0 2 13 2 1 2 14 2 2 2 15 2 3 2 16 2 4 2 17 2 5 2 18 2 6 2 19 2 7 2 20 2 0, 1 2 21 2 2, 3 2 22 2 4, 5 2 23 2 6, 7 2 24 2 0, 4 2 25 2 2, 6 2 26 2 0, 1, 4 2 27 2 2, 3, 6 2 28 2 0, 1, 4, 5 2 29 2 2, 3, 6, 7 2 30 2 0, 2, 4, 6 2 31 Reserved Reserved Reserved

Table 8 shows an example of the Rel-16 DMRS table defined based on the Rel-15 DMRS table of Table 7 described above. Table 8 is just an example for convenience of the description and does not limit the technical scope of the present disclosure. Accordingly, it is apparent that the Rel-16 DMRS table is not limited to an example of Table 8, and can be expanded to another combination of the DMRS ports in a form having the same feature.

TABLE 8 One Codeword: Two Codewords: Codeword 0 enabled, Codeword 0 enabled, Codeword 1 disabled Codeword 1 enabled Number Number of of DMRS Number DMRS Number CDM of CDM of group(s) front- group(s) front- without DMRS load without DMRS load Value data port(s) symbols Value data port(s) symbols  0 1 0 1 0 2 0-4 2  1 1 1 1 1 2 0, 1, 2, 3, 4, 6 2  2 1 0, 1 1 2 2 0, 1, 2, 3, 4, 5, 6 2  3 2 0 1 3 2 0, 1, 2, 3, 4, 5, 6, 7 2  4 2 1 1 4 1 0 1  5 2 2 1 5 1 1 1  6 2 3 1 6 1 0, 1 1  7 2 0, 1 1 7 2 0 1  8 2 2, 3 1 8 2 2 1  9 2 0-2 1 9 2 0, 1 1 10 2 0-3 1 10 2 2, 3 1 11 2 0, 2 1 11 2 0 2 12 2 0 2 12 2 2 2 13 2 1 2 13 2 0, 1 2 14 2 2 2 14 2 2, 3 2 15 2 3 2 15-31 reserved reserved reserved 16 2 4 2 17 2 5 2 18 2 6 2 19 2 7 2 20 2 0, 1 2 21 2 2, 3 2 22 2 4, 5 2 23 2 6, 7 2 24 2 0, 4 2 25 2 2, 6 2 26 2 0, 1, 4 2 27 2 2, 3, 6 2 28 2 0, 1, 4, 5 2 29 2 2, 3, 6, 7 2 30 2 0, 2, 4, 6 2 31 Reserved Reserved Reserved

Referring to Table 8, when codepoints corresponding to values 4 to 14 are indicated to the UE upon transmission of two CWs, the UE may know that the corresponding operation is the URLLC operation.

Specifically, one operation of multiple URLLC operations may be configured to the UE through the higher layer signaling according to the method of Proposal 1 described above, and the UE may know which scheme should be performed. In this case, the Rel-16 DMRS table may be applied to the value indicted through the DMRS port indication field of the DCI, and a detailed operation may be assumed as below according to the scheme configured to the UE through the higher layer signaling (Meanwhile, when one value of values 0 to 3 is indicated to the UE, the operation may be performed similarly to the Rel-15 DMRS table. That is, the transmission may be interpreted as transmission of two CWs corresponding to different TBs.).

For example, it may be assumed that when scheme 2a is configured through the higher layer signaling, if one value of values 4 to 14 is indicated, multiple TCI states indicted to the UE are mapped to different frequency domains. In this case, TB information for determining a TB size may be defined according to a fixed rule to be based on a specific value of TBs 1 and 2, or configured through signaling between the BS and the UE. In this case, a value of a TB field not applied to determination of the TB size may be fixed to a combination of specific MCS, RV, and NDI values. For example, upon receiving DCI in which MCS=0 and RV=0 are configured, the UE may know that the TB field of the corresponding DCI is not used for determining the TB size.

For example, it may be assumed that when Scheme 213/3/4 is configured through the higher layer signaling, if one value of values 4 to 14 is indicated, different CWs transmitted to the UE are based on the same TB (i.e., different CWs are encoded from the same TB). That is, the UE may assume that two CWs are mutually repeatedly transmitted CWs. In this case, the TB information for determining the TB size may be defined according to a fixed rule to be based on a specific value of TBs 1 and 2, or configured through signal exchange between the BS and the UE.

In this case, a value of a TB field not applied to determination of the TB size may be fixed to a combination of specific MCS, RV, and NDI values. For example, the value of the TB field may be defined as MCS=0 and RV=0. Alternatively, the value of the TB field not applied to determination of the TB size may be used as a usage for indicating a modulation order of repeatedly transmitted CW and/or the RV value. In this case, a TB field for determining the TB size and a TB field for determining the modulation order/RV for a TB corresponding to a specific CW may be different. For example, the TB size is determined based on the MCS of field TB 1 for CW #2 (or CW #1), but the modulation order/RV may adopt a value indicated by field TB 2.

Each codepoint of Table 8 may have the following features.

First, the maximum number of UEs which are multi-user (MU) paired is limited to 2. The reason is that when the number of UEs which is MU paired increases, mutual interference may increase, and as a result, capability deterioration may occur. Accordingly, the mutual interference may be reduced by limiting the maximum number of UEs which are enabled to be MU paired.

Second, the UEs which are MU paired are indicated by DMRS ports of different CDM groups. The reason is that when the UEs which are MU paired are indicated by DMRS ports of the same CDM group, interference between the DMRS ports may increase. Accordingly, the DRMS ports of different CDM groups are allocated to different UEs to reduce mutual interference. Meanwhile, in the case of value 4/5, it is assumed that the DMRS ports of the same CDM group may be allocated to different UEs, and the reason is that it may be assumed that the PDSCH may be together multiplexed to the DMRS symbol, and more robust channel coding may be used.

In the example, it is assumed that one value of the URLLC schemes (e.g., schemes 2a, 2b, 3, and 4) is configured in advance through the higher layer signaling, but even otherwise, the method for dynamically indicating the URLLC operation may be supported based on the proposal. For example, in a state in which the UE is configured to use the Rel-16 DMRS tables, multiple TCI states may be indicated to the UE through the DCI, and when 2 CW transmission is indicated, whether a specific operation corresponding to one of the URLLC schemes (e.g., schemes 2a, 2b, 3, and 4) is performed may be dynamically indicated through a specific codepoint(s) of the DMRS port indication field. To this end, different codepoint(s) may be defined to correspond to different schemes. For example, in the example of Table 8, values 4 to 14 may correspond to scheme 2a, and values 15 to 31 may be utilized for defining the DMRS ports combination corresponding to scheme 2b/3/4.

As in the proposed method described above, the UE may be configured with the URLLC operation scheme based on the higher layer signaling. Further, the UE may be configured with a higher layer parameter related to the corresponding URLLC operation together with the URLLC operation scheme. For example, in addition to the operation scheme, additional parameters (e.g., the number of repetition times, a repetition period, etc.) required for performing the corresponding operation scheme may be together configured in the higher layer parameter. As such, it may be anticipated that the BS which intends to indicate the URLLC operation to the UE will configure the higher layer parameter related to the URLLC operation to the UE. On the contrary, in the case of a UE not requiring the URLLC operation, the higher layer parameter related to the URLLC operation may not be configured. Accordingly, the UE may differently interpret the DMRS port indication field based on whether to configure the higher layer parameter related to the URLLC operation.

For example, (i) when the UE is configured with the higher layer parameter related to the URLLC operation, a specific bit of the DMRS port indication field may be used as a usage for dynamically indicating the URLLC operation according to the proposal. On the contrary, (ii) when the UE is not configured with the higher layer parameter related to the URLLC operation, the specific bit of the DMRS port indication field may be used as a usage for indicating single TRP transmission or dynamic point selection from multi-TRP. As an example for the (ii) operation, when the UE indicated with multiple TCI states is indicated with a specific codepoint through the DMRS port indication field, the UE may assume the single TRP transmission or dynamic point selection from multi-TRP other than the multi-TRP transmission. As an example of the specific codepoint, there may be a codepoint indicating a case where the DMRS port combination indicated to the UE is included in a single CDM group.

Meanwhile, in respect to the URLLC operation, whether the URLLC operation is performed may be configured to the UE based on a higher layer configuration and/or RNTI and/or a specific field(s). In this case, when different TB fields (e.g., TB field 1/TB field 2) are defined in the DCI, the UE may also assume that a second CW is disabled regardless of an MCS/RV/NDI value indicated through the TB field for the specific TB field. When it may be assumed that a second C2 is disabled, since single CW transmission may be performed while using two different TB fields, there is an advantage in that different MCS/RV values may be indicated for different transmission occasions in the URLLC scheme.

An M-TRP URLLC operation or M-TRP eMBB operation may be configured based on the method of Proposal 1 described above, and a specific scheme among multiple schemes of the M-TRP URLLC operation may be additionally configured/enabled.

<Proposal 2>

In relation to the URLLC operation, scheme 3 and scheme 4 of Table 6 described above correspond to a repeated transmission scheme of the time domain. Proposal 2 of the present disclosure proposes a method for configuring/indicating the number of transmission times for repeated transmission for scheme 3 and scheme 4. As a method for configuring/indicating the total number of repeated transmission times, a method for configuring a specific value to the UE through the higher layer parameter or indicating the number of repeated transmission times based on the specific field in the DCI may be considered. Hereinafter, the method for configuring the number of repeated transmission times by considering the URLLC operation scheme will be described in detail.

Scheme 3 may mean repeated transmission achieved in units of mini-slot by a TDM based scheme. For scheme 3, 2, 4, and 7 symbols unit transmission occasions may be defined. In Scheme 3 (TDM), n (n<=Nt1) TCI states may be indicated together with non-overlapped time resource allocation. Each transmission occasion of the TB has one TCI and one RV together with the time granularity of the mini-slot. All transmission occasion(s) in the slot uses a common MCS together with the same single or multiple DMRS port(s). The RV/TCI state may be the same or different between the transmission occasions.

As the method for configuring the number of repeated transmission times, a method for determining the total number of repeated transmission times according to the configured/indicated number of TCI states is proposed. In other words, the total number of repeated transmission times may be determined according to the configured/indicate number of TCI states.

For example, multiple TCI states for repeated transmission may be indicated through ‘Transmission configuration indication’ field (hereinafter, may be referred to as a TCI state field) defined for indicating the ICI state in the DCI (e.g., DCI format 1_1). Each codepoint in the TCI state field may correspond to one or more TCI state values, and codepoints corresponding to multiple TCI states are indicated to the UE to configure/indicate multiple TCI states to the corresponding UE.

For example, when the number of TCI states is 4, each symbol granularity (i.e., transmission occasion) may be repeated four times. As an example, when the transmission occasion is a 2 symbol granularity, the 2 symbol granularity may be repeated four times (2++2++2++2). As an example, when the transmission occasion is a 4 symbol granularity, the 4 symbol granularity may be repeated four times (4++4++4++4). As an example, when the transmission occasion is a 7 symbol granularity, the 7 symbol granularity may be repeated four times (7++7++7++7),

As another example, when the number of TCI states is 2, each symbol granularity may be repeated two times. As an example, when the transmission occasion is the 2 symbol granularity, the 2 symbol granularity may be repeated two times (2++2). As an example, when the transmission occasion is the 4 symbol granularity, the 4 symbol granularity may be repeated two times (2+4). As an example, when the transmission occasion is the 7 symbol granularity, the 7 symbol granularity may be repeated two times (2+7).

A reason why the total number of repeated transmission times may be defined according to the configured/indicated number of TCI states as in the example is that repeated transmission exceeding the configured/indicated number of TCI states may be replaced with a mini-slot structure constituted by more symbol(s). In the above description, the ‘mini-slot structure’ may mean a scheduling structure having a granularity of 2, 4, 6, or 7 symbols which may be indicated by PDSCH mapping type B.

When the configured/indicated number of TCI states and the number of repeated transmission times are expressed as x and y, respectively, a case where x is larger than y may be regarded as a case of repeated transmission exceeding the configured/indicated number of TCI states.

For example, when the configured/indicated number of TCI states is 2 and a mini-slot having a structure of 2 symbols is repeated four times, a 2+2+2+2 structure is provided, and this may be replaced with repeating a mini-slot having a structure of four symbols two times. That is, (in terms of considering DMRS overhead), a scheme of repeating the mini-slot having the structure of fourth symbols two times may be more efficient than a scheme of repeating the mini-slot having the structure of two symbols four times. Since the configured/indicated number of TCI states is 2 in the example, when the TCI states are repeatedly transmitted four times, the same TCI states are repeatedly shown. However, when this is repeatedly transmitted two times by using a larger mini-slot structure, there is an advantage in that the same TCI states are not repeated, and the DMRS overhead may be reduced most of all. Similarly to the example, even with respect to a case where the configured/indicated number of TCI states is 4 and the mini-slot having the structure of 2 symbols is repeated eight times, a 2+2+2+2+2+2+2+2 structure may be similarly replaced with the 4+4+4+4 structure.

Accordingly, as described in the example, the number of repeated transmission times exceeding the configured/indicated number of TCI states may be replaced with a mini-slot structure having another number of symbols, and as a result, capability enhancement may be anticipated through an effect of reducing the DMRS overhead.

In conclusion, the number of repeated transmission times may be indicated through the number of TCI states indicated to the UE. That is, the number of repetition times of the transmission occasion may be determined based on the number of TCI states corresponding to the codepoints of the TCI field in the DCI. For example, when 2 TCI states are indicated to the UE, the total number of transmission occasions may be 2 and the repeated transmission may be made two times, and when 4 TCI states are indicated, the total number of transmission occasions may be 4 and the repeated transmission may be made four times. In addition, a QCL assumption for each transmission occasion may sequentially apply the TCI states indicated to the UE. For example, the transmission occasions may be sequentially mapped in such a manner that a 1st transmission occasion is mapped to a 1st TCI state and a 2nd transmission occasion is mapped to a 2nd TCI state.

Meanwhile, scheme 4 (TDM) may mean repeated transmission made in the slot granularity. In Scheme 4, n (n<=Nt2) TCI states may be indicated in K (n<=K) different slots. Each transmission occasion of the TB has one TCI and one RV. All transmission occasion(s) across K slots uses a common MCS together with the same single or multiple DMRS port(s). The RV/TCI state may be the same or different among the transmission occasion(s).

Latency of scheme 4 cannot but become longer due to a feature that the repeated transmission is made in the slot granularity, and as a result, it may be more preferable to use scheme 4 as a usage for increasing reliability than the latency. In this case, since the reliability may be enhanced by increasing a reception SNR through the repeated transmission, the number of repeated transmission times larger than the indicated number of TCI states may be considered.

Accordingly, in the case of scheme 4, the number of repeated transmission times may be configured through the higher layer signaling (e.g., RRC/MAC CE). For example, a higher layer parameter (e.g., repetitionnumber) for configuring the number of repeated transmission times may be defined, and the number of repeated transmission times may be configured through the corresponding parameter. As an example, the number of repeated transmission times may be configured to one of 2, 3, 4, 5, 6, 7, 8, or 16.

Alternatively, even in the case of scheme 4, a method for dynamically indicating, by the BS, the number of repeated transmission times to the UE may be considered. In this case, there are an advantage in that a signaling method defined for M-TRP based URLLC such as scheme 3 may be utilized as it is, and an advantage in that the repetition number is dynamically adjusted even for scheme 4 by considering various service types, and as a result, the latency may be adjusted according to a specific service type. As the signaling method for dynamically indicating the number of repeated transmission times for the case of scheme 4 to the UE, the following proposed may be adopted.

The BS may configure information related to the number of repeated transmission times applicable to scheme 4 to the UE through the higher layer signaling (e.g., RRC/MAC CE). For example, a candidate value(s) for the applicable number of repeated transmission times may be indicated. Alternatively, a candidate value(s) for the number of repeated transmission times fixed or predefined between the BS and the UE may be defined. The candidate value may mean some/all values which the BS configures to the UE through the higher layer signaling based on a pre-configured/defined promise/rule/condition among the numbers of repeated transmission times applicable to scheme 4 above.

The BS may explicitly or implicitly a specific value among the candidate value(s) for the number of repeated transmission times which may be indicated to the UE through a specific field in the DCI. The specific field in the DCI may be a field newly defined for the number of repeated transmission times or a conventional field (e.g., the TCI state field, the antenna port(s) field, the MCS field, the NDI field, the RV field, etc.).

For example, when the number of repeated transmission times applicable to scheme 4 above is configured to the UE through the higher layer signaling, it may be assumed that {2, 4, 8, 16} is defined as the applicable number of repeated transmission times. {2, 4, 8, 16} is just an example of the candidate values for the number of repeated transmission times, and does not limit the technical scope of the present disclosure. Accordingly, it may be possible that the number of repeated transmission times is configured to another value (e.g., 2, 3, 4, 5, 6, 7, 8, 16, etc.). Alternatively, the some number of transmission times among the values, as an example, value such as {2, 8} may be configured to the UE through the higher layer signaling. In addition, a specific value of the candidate value(s) (e.g., {2, 8}) may be indicated through the specific field in the DCI.

Hereinafter, examples of the method for dynamically indicating the number of repeated transmission times through the specific field in the DCI will be described.

Example 1) The number of repeated transmission times may be indicated by using the TCI state field in the DCI.

For example, the number of repeated transmission times may be mapped to the codepoint of the TCI state field, and the BS may indicate the specific number of repeated transmission times to the UE through/using the codepoint value indicated to the UE through the TCI state field. As a specific example, a repetition number corresponding to {2} may be mapped to a value in which the codepoint of the TCI state field corresponds to 0 (i.e., 000) to 3 (i.e., 011), and a repetition number corresponding to {8} may be mapped to a value in which the codepoint corresponds to 4 (i.e., 100) to 7 (i.e., 111). For example, a mapping relationship between the codepoint and the repetition number may be pre-defined between the UE and the BS.

As another example, a method for indicating whether repeated transmission corresponding to a relevant specific repetition number is performed through the specific field in the DCI after the specific repetition number is configured to the UE through the higher layer signaling may also be considered. For example, the repetition number corresponding to {2} may be configured through the higher layer signaling, and whether the repeated transmission corresponding to the relevant repetition number is performed may be indicated through a codepoint of a specific TCI state field. For example whether the repeated transmission corresponding to the relevant repetition number (e.g., 2) may be enabled through the codepoint of the specific TCI state field. Further, as in the following example, information on whether the repeated transmission being performed may also be indicated through the specific field in the DCI.

Example 2) Modulation and Coding Scheme (MCS)/New Data Indicator (NDI)/Redundancy Version (RV) fields for a second transport block (TB) of the DCI may be used. For example, different repeated transmission numbers may be mapped to a codepoints corresponding to the MCS, NDI, and RV fields for the second TB, and the BS may indicate, to the UE, a specific repeated transmission number through the relevant field.

Example 3) The antenna port(s) field of the DCI may be used. Even in Example 3, it is assumed that the values such as {2, 8} are configured to the UE through the higher layer signaling. For example, a specific repetition number may be indicated based on a rank value (e.g., DRMS port(s) number) or/and the number of CDM groups or/and an index of the CDM group indicated through the antenna port(s) field.

As an example, when the rank value is equal to or smaller than a specific value (and/or a pre-configured/defined value), a smaller value (e.g., {2}) of the repetition numbers (e.g., {2, 8}) configured through the higher layer signaling may be indicated. On the contrary, when the rank value is larger than the specific value, a larger value (e.g., {8}) of the repetition numbers (e.g., {2, 8}) configured through the higher layer signaling may be indicated.

As an example, when the indicated number of CDM groups is 2 or more, i.e., when the indicated DMRS port(s) are included in different CDM groups, the smaller repetition number of the repetition numbers (e.g., {2, 8}) configured through the higher layer signaling may be indicated, and when the indicated number of CDM groups is 1, i.e., when the indicated DMRS port(s) are included in the same CDM group, a larger repetition number may be indicated. Alternatively, when the indicated number of CDM groups is 2 or more, i.e., when the indicated DMRS port(s) are included in different CDM groups, the larger repetition number may be indicated, and when the indicated number of CDM groups is 1, i.e., when the indicated DMRS port(s) are included in the same CDM group, a smaller repetition number may be indicated.

As an example, when the indicated CDM group index is 0, i.e., when the indicated DMRS port(s) are included in CDM group 0, the smaller repetition number may be indicated, and when the indicated CDM group index is 1, i.e., when the indicated DMRS port(s) are included in CDM group 1, the larger repetition number may be indicated. Alternatively, when the indicated CDM group index is 0, i.e., when the indicated DMRS port(s) are included in CDM group 0, the larger repetition number may be indicated, and when the indicated CDM group index is 1, i.e., when the indicated DMRS port(s) are included in CDM group 1, the smaller repetition number may be indicated.

Example 4) Example 4 is another example using the antenna port(s) field. When the DMRS antenna port index is indicated to the UE through the antenna port(s) field, the repeated transmission number is jointly encoded to indicate the repeated transmission number to the UE jointly with the DMRS antenna port.

Table 9 shows an example in which a repeated transmission number corresponding to the DMRS antenna port is jointly encoded and indicated. Table 9 is just an example for convenience of description, and does not limit the technical scope of the present disclosure, and it is apparent that Table 9 may be extended to another form by applying a feature of the proposed method described in the present disclosure. For example, a DMRS port corresponding to each value of the codepoint which may be indicated through the antenna port field may be pre-defined and the repeated transmission number may be additionally pre-defined/configured to correspond to each codepoint jointly with the DMRS port.

TABLE 9 One Codeword: One Codeword: Codeword 0 enabled, Codeword 0 enabled, Codeword 1 disabled Codeword 1 disabled Number Number of DMRS of DMRS CDM CDM the group(s) group(s) number without DMRS without DMRS of Value data port(s) Value data port(s) repetition  0 1 0 0 1 0 k1  1 1 1 1 1 1 k1  2 1 0, 1 2 1 0, 1 k1  3 2 0 3 2 0 k1  4 2 1 4 2 1 k1  5 2 2 5 2 2 k1  6 2 3 6 2 3 k1  7 2 0, 1 7 2 0, 1 k1  8 2 2, 3 8 2 2, 3 k1  9 2 0-2 9 2 0 k2 10 2 0-3 10 2 1 k2 11 2 0, 2 11 2 0, 2 k1 12-15 Reserved Reserved 12 2 2 k2 13 2 3 k2 14 2 0, 1 k2 15 2 2, 3 k2

In Table 9, a left side shows an example of the antenna port(s) field defined in the current standard (see TS38.212 table 7.3.1.2.2-1). A right side shows an example of an enhanced antenna port(s) field to which the proposed method of the present disclosure is applied. Referring to Table 9, in a right table, values 9, 10, and 12 to 15 are newly added parts, and an example of the enhanced DMRS table may have the following feature.

First, the total number of transmission layers may be limited. Since high throughput is not required in the URLLC operation, a large number of transmission layers may not be supported. Accordingly, it may be newly defined that the number of transmission layers is limited to a specific value or less and a codepoint indicating a value exceeding the relevant number of layers indicates another value. In the example of the DMRS table, values corresponding to values 9 and 10 originally define a DMRS port(s) combination capable of indicating 3 and 4 layers, but may be defined to correspond to another value by applying the number of transmission layers being limited to the specific value (e.g., 2) or less.

Second, a specific codepoint of a relevant field may be mapped to a specific repeated transmission number. In the example of the enhanced DMRS table, k1 and k2 may correspond to the specific repeated transmission number. k1 and k2 may become values configured through the higher layer signaling or defined by a static rule between the BS and the UE. In the example of the DMRS table, values 3, 4, 5, 6, 7, and 8 and values 9, 10, 12, 13, 14, and 15 indicate the same DMRS port index and CDM group number (‘number of DMRS CDM group(s) without data’), but there is a feature that each repeated transmission number is different as k1 or k2.

Although not applied in the example of the DMRS table, the number of CDM groups may also be limited to a specific value in order to support new more combinations for the DMRS ports and the repeated transmission times. For example, when only 2 is limited to be supported as the number of CDM groups in Example 4 above, values corresponding to values 0, 1, and 2 may correspond to a new combination.

Example 5) Another example using the antenna port(s) field of the DCI is proposed. A specific repetition number may be indicated based on the index of the DMRS antenna port(s) indicated through the antenna port(s) field.

For example, a specific repeated transmission number may be mapped to a specific DRMS antenna port or DMRS antenna ports (i.e., DMRS antenna port group).

Table 10 shows an example of mapping and configuring the repeated transmission number for each DMRS antenna port. That is, Table 10 shows an example in which different repeated transmission numbers are mapped to different DMRS antenna ports. Table 11 shows an example of mapping and configuring the repeated transmission number for each DMRS antenna port group. That is, Table 11 shows an example in which different repeated transmission numbers are mapped by a group granularity constituted by multiple DMRS antenna ports.

TABLE 10 Type 1 Type 2 DMRS the number DMRS the number port of repetition port of repetition 0 k1 0 k1 1 k2 1 k2 2 k3 2 k3 3 k4 3 k4 4 k5 4 k5 5 k6 5 k6 6 k7 6 k7 7 k8 7 k8 8 k9 9  k10 10  k11 11  k12

TABLE 11 Type 1 Type 2 the number the number DMRS port of repetition DMRS port of repetition 0 k1 0 k1 1 k1 1 k1 2 k2 2 k2 3 k2 3 k2 4 k3 4 k3 5 k3 5 k3 6 k4 6 k4 7 k4 7 k4 8 k5 9 k5 10 k6 11 k6

In the examples of Tables 10 and 11, k1 to k12 mean different repeated transmission numbers. In this case, some of the values of k1 to k12 may correspond to the same value. The repeated transmission numbers (the values of k1 to k12) may be configured to the UE through the higher layer signaling or a specific value may be defined by a static rule between the BS and the UE.

Referring to Table 10, different repeated transmission numbers may be indicated according to the DMRS port index indicated to the UE. For example, when Table 10 is assumed, in a case where DMRS port 0 is indicated to the UE, the repeated transmission number corresponding to k1 may be indicated and in a case where DMRS port 1 is indicated, the repeated transmission number corresponding to k2 may be indicated.

Referring to Table 11, the repeated transmission number may be mapped and configured by the group granularity, and the same repeated transmission number may be mapped to DMRS antenna ports in the same group. As an example, in Table 11, DMRS ports 0 and 1 may be configured as one group, and the repeated transmission number k1 may be configured in the relevant group.

In the example of Table 11 above, each group is constituted by same DMRS port number (e.g., 2), but different DMRS port numbers may also be configured for each group. Even in this case, the same repeated transmission number may be configured in the DMRS ports in the same group.

Meanwhile, when multiple DMRS ports are indicated to the UE, the UE may assume a repeated transmission number corresponding to a specific DMRS port (if repeated transmission numbers corresponding to the DMRS ports are different). For example, a repeated transmission number corresponding to a higher or lower index may be defined to be followed. As an example, when DMRS ports 0 and 1 are indicated, and defined to correspond to the lower index, the repeated transmission number of k1 corresponding to DMRS port 0 may be indicated.

In addition to the proposal, a method for indicating different repeated transmission numbers according to the order of the DMRS port index in the same CDM group may also be considered. That is, different repeated transmission numbers may be configured for the DMRS ports in the same CDM group, respectively. This may also be interpreted as mapping a specific repeated transmission number to the DMRS antenna port group constituted by the DMRS antenna ports included in different CDM groups. In other words, DMRS ports in which the same repeated transmission number is configured may correspond to different CDM groups.

Table 12 shows an example in which different repeated transmission numbers are mapped according to the order of the DMRX port index in the same CDM group. Table 12 is just an example for convenience of the description and does not limit the technical scope of the present disclosure.

TABLE 12 Type 1 Type 2 CDM CDM group DMRS the number group DMRS the number index port of repetition index port of repetition 0 0 k1 0 0 k1 1 k2 1 k2 4 k3 6 k3 5 k4 7 k4 1 2 k1 1 2 k1 3 k2 3 k2 6 k3 8 k3 7 k4 9 k4 2 4 k1 5 k2 10 k3 11 k4

In the example of Table 12, k1 to k4 mean different repeated transmission numbers. In this case, some of the values of k1 to k4 may correspond to the same value. The repeated transmission numbers (e.g., the values of k1 to k12) may be configured to the UE through the higher layer signaling or a specific value may be defined by a static rule between the BS and the UE.

Referring to Table 12, different repeated transmission numbers may be indicated according to the order in the CDM group including the relevant DMRS ports based on the DMRS port index indicated to the UE. In other words, the repeated transmission numbers of k1 to k4 may be configured/defined, and may sequentially correspond to k1 to k4, respectively sequentially based on an indication order of the DMRS port. For example, when DMRS configuration type 1 is assumed, as DMRS port 0 is indicated to the UE, the repeated transmission number corresponding to k1 may be indicated and as DMRS port 4 is indicated, the repeated transmission number corresponding to k3 may be indicated.

Meanwhile, when multiple DMRS ports are indicated to the UE, the UE may assume a repeated transmission number corresponding to a specific DMRS port (if repeated transmission numbers corresponding to the DMRS ports are different). For example, a repeated transmission number corresponding to a higher or lower index may be defined to be followed. As an example, when DMRS ports 0 and 1 are indicated, and defined to correspond to the lower index, the repeated transmission number of k1 corresponding to DMRS port 0 may be indicated.

When different repeated transmission numbers are indicated according to the order of the DMRX port index in the same CDM group as in the example described above, there may be the following advantage.

When a situation of multi-user (MU)-pairing assuming scheme 3 or scheme 4 is considered, it is more natural that a small number of UEs are MU-paired than a large number of UEs are MU-paired. The reason is that MU-pairing is primarily used for a purpose of increasing a data transmission rate by simultaneously transmitting data to multiple UEs, and to this end, precoding orthogonal to different UEs should be able to be applied so as to prevent interference between UEs. However, in the case of URLLC, it is preferable to minimize interference with another UE and further, in order to reduce a latency time, urgent data transmission may be performed, and in this case, it may be difficult and not preferred to find a UE having precoding orthogonal for a short time. Accordingly, when it is assumed that a small number of UEs are MU-paired, different UEs may be supported through the DMRS port(s) included in different CDM groups. The reason is that it is anticipated that interference between DMRS ports which are multiplexed based on FDM upon channel estimation is smaller than interference between DMRS ports which are multiplexed based on CDM.

When a situation is assumed in which different UEs are supported through DMRS port(s) included in different CDM groups, different repeated transmission numbers should be able to be indicated to the respective UEs through the DMRS port(s) in the same CDM group. For example, when the maximum number of symbols of the DMRS is 1 and DMRS type 1 is assumed, DMRS ports 0 and 1 and DMRS ports 2 and 3 are included in CDM groups 0 and 1, respectively. In this case, when DMRS ports 0 and 1 correspond to the same repeated transmission number and DMRS ports 2 and 3 correspond to the same repeated transmission number, there is no method capable of indicating different repeated transmission numbers to different respective UEs. Accordingly, it may be regarded that it is preferable that different repeated transmission numbers correspond to different DMRS port(s) in the same CDM group. Accordingly, according to the proposed method, different repeated transmission numbers may be mapped according to the order of the DMRS port index in the same CDM group, and a specific repeated transmission number may be indicated according to the DMRS port index indicated to the UE.

Table 13 shows another example in which different repeated transmission numbers are mapped according to the order of the DMRX port index in the same CDM group according to the method proposed in the present disclosure. Table 13 is just an example for convenience of the description and does not limit the technical scope of the present disclosure.

TABLE 13 Type 1 Type 2 CDM the CDM the group DMRS number of group DMRS number of index port repetition index port repetition 0 0 k1 0 0 k1 1 k2 1 k2 4 k3 6 k3 5 k4 7 k4 1 2 k2 1 2 k2 3 k1 3 k1 6 k4 8 k4 7 k3 9 k3 2 4 k1 5 k2 10 k3 11 k4

When the example of Table 13 is compared with Table 12, there is a feature that repeated transmission numbers corresponding to DMRS ports included in CDM group 1 are different. This has a feature that when multiple DMRS ports are indicated to the UE, the UE may assume a repeated transmission number corresponding to a specific DMRS port (if the repeated transmission numbers corresponding to the DMRS ports are different), and indicate different repeated transmission numbers through a combination of DMRS ports included in different CDM groups. For example, when a repeated transmission number corresponding to a higher or lower index is defined to be followed, different repeated transmission numbers may be configured through the combination of the DMRS ports included in different CDM groups.

For example, when Table 12 and the repeated transmission number corresponding to the small DMRS port are defined to be followed, the repeated transmission number corresponding to k1 may be indicated for each of the combination of DMRS ports 0 and 1 and the combination of DMRS ports 2 and 3. On the contrary, when Table 13 above is assumed, the repeated transmission number corresponding to k1 may be indicated for DMRS ports 0 and 1 and the repeated transmission number corresponding to k2 may be indicated for DMRS ports 2 and 3.

Meanwhile, in addition to matters presented in the examples of Tables 10, 11, 12, and 13, the repeated transmission number corresponding to each DMRS port may be defined differently according to the maximum symbol number (‘maxLength’) of the DMRS configured to the UE.

Table 14 shows an example of differently defining the repeated transmission number corresponding to each DMRS port according to the maximum symbol number of the DMRS by assuming Table 13 above. Table 14 is just an example for convenience of the description and does not limit the technical scope of the present disclosure.

TABLE 14 maxLength = 1 maxLength = 2 Type 1 Type 2 Type 1 Type 2 the the the the CDM number CDM number CDM number CDM number group DMRS of group DMRS of group DRMS of group DMRS of index port repetition index port repetition index port repetition index port repetition 0 0 k1 0 0 k1 0 0 k1 0  0 k1 1 k2 1 k2 1 k3  1 k3 4 k2  6 k2 5 k4  7 k4 1 2 k2 1 2 k2 1 2 k1 1  2 k1 3 k1 3 k1 3 k3  3 k3 6 k2  8 k2 7 k4  9 k4 2 4 k1 2  4 k1 5 k2  5 k3 10 k2 11 k4

Referring to Table 14, the repeated transmission numbers corresponding to the DMRS ports may be differently defined for a case where the maximum symbol number is 1 (i.e., maxlength=1) and a case where the maximum symbol number is 2 (i.e., maxlength=2), respectively.

In the case where the maximum symbol number is 1, the repeated transmission numbers corresponding to k1 and k2 may be indicated by using DMRS ports in different CDM groups, respectively in the case of 1 layer transmission and k1 and k2 may be indicated by using a (0, 1) combination and a (2, 3) combination, respectively by assuming that the repeated transmission number corresponding to the small DMRS port is followed in the case of 2 layer transmission. On the contrary, in the case where the maximum symbol number is 2, the repeated transmission numbers corresponding to k1, k2, k3, and k4 may be indicated by using DMRS ports in different CDM groups, respectively in the case of 1 layer transmission, and k1 and k2 may be indicated by using the (0, 1) combination and a (4, 5) combination, respectively by assuming that the repeated transmission number corresponding to the small DMRS port is followed, and k1 and k2 may be indicated by using the (2, 3) combination and a (6, 7) combination, respectively.

That is, in the example, there is a feature that in the case where the maximum symbol number of the DMRS is 1, different repeated transmission numbers may be indicated through the DMRS port combination in different CDM groups upon the 2 layer transmission, and in the case where the maximum symbol number is 2, different repeated transmission numbers may be indicated through the DMRS port combination in the same CDM group upon the 2 layer transmission.

When Table 13 and Table 14 are compared, the repeated transmission numbers corresponding to k1, k2, k3, and k4 may be indicated upon the 2 layer transmission, and as a result, there may be an advantage in that more various repeated transmissions numbers may be indicated when assuming one UE. Meanwhile, in the case of Table 14, the repeated transmission numbers corresponding to k1 and k2 may be indicated upon the 2 layer transmission, but the same repeated transmission number may be indicated in each of different CDM groups, and as a result, there may be an advantage in that independent repeated transmission numbers may be indicated to different UEs when the MU-pairing is considered.

Since the method and/or embodiment (e.g., examples 1 to 5) may be applied to a case where the repeated transmission is intended to be performed in the time domain as described above, it is apparent that scheme 3 and/or scheme 4 are/is applicable. Further, the method and/or embodiment (e.g., examples 1 to 5) may become one example applicable to the methods of Proposal 2, and are/is not limited to the example(s). Further, it is apparent that another embodiment(s) may be applied based on the feature of the proposed method. Further, the method and/or embodiment (e.g., examples 1 to 5) may be independently applied or may also be applied as a method of a form in which multiple proposed methods are combined.

The repeated transmission number of the transmission occasion may be configured based on the method and/or embodiment (e.g., examples 1 to 5). That is, the number of multiple transmission occasions received by the UE may be known.

<Proposal 2-1>

The method and/or embodiment (e.g., examples 1 to 5) may also be used as a method for indicating the number of shifting symbols between different transmission occasions in the case of scheme 3.

In the case of scheme 3, the shifting symbol between different transmission occasions may mean a degree at which different transmission occasions are separated from each other.

FIG. 11 illustrates an example of a configuration of a shifting symbol between transmission occasions.

Referring to FIG. 11, according to definition 1, the shifting symbol may mean the number of symbols from a last symbol of a first transmission occasion up to a first symbol of a second transmission occasion. In this case, the shifting symbol may also be replaced with a gap symbol and expressed. For example, the shifting symbol (gap symbol) may also be interpreted as a gap between the first transmission occasion and the second transmission occasion. According to definition 2, the shifting symbol may mean the number of symbols from the first symbol of the first transmission occasion up to the first symbol of the second transmission occasion. In the following description, the shifting symbol will be described according to definition 1. However, this is just for convenience of the description and does not limit the scope of the present disclosure. Accordingly, this is applicable even to the case according to definition 2.

In the case of scheme 3, a reason for requiring the shifting symbol is to support the repeated transmission to be performed in one slot even when a DL/UL symbol is changed in one slot.

Table 15 shows a partial example of a slot format for a normal CP (see Table 11.1.1-1 of TS 38.213). Referring to Table 15, symbols for DL (D) and UL (U) may be repeatedly configured in one slot.

TABLE 15 Symbol number in a slot Format 0 1 2 3 4 5 6 7 8 9 10 11 12 13 46 D D D D D F U D D D D D F U 47 D D F U U U U D D F U U U U 48 D F U U U U U D F U U U U U 49 D D D D F F U D D D D F F U 50 D D F F U U U D D F F U U U 51 D F F U U U U D F F U U U U 52 D F F F F F U D F F F F F U 53 D D F F F F U D D F F F F U 54 F F F F F F F D D D D D D D 55 D D F F F U U U D D D D D D

FIG. 12 illustrates an example of a transmission occasion repeatedly transmitted in one slot. FIG. 12 is just for convenience of the description and does not limit the technical scope of the present disclosure.

FIG. 12 illustrates an example of applying the repeated transmission to a slot format corresponding to Value 49 in Table 15 above. In FIG. 12, Case 1 shows an example of the repeated transmission when the DL/UL symbol change is not considered in one slot. In this case, a problem occurs in that the second transmission occasion may not be transmitted while being overlapped with a symbol for actual UL transmission. On the contrary, Case 2 shows an example of performing the repeated transmission only in a symbol for DL transmission by considering the DL/UL symbol change in one slot. When the BS intends to perform the repeated transmission by considering the DL/UL symbol change in one slot as such, the BS need to announce, to the UE, the number of shifting symbols between different transmission occasions.

For example, the number of shifting symbols between different transmission occasions may be configured based on the method and/or embodiment (e.g., examples 1 to 5). As an example, the number of shifting symbols (gap symbols) may be configured through the higher layer signaling. As an example, the number of shifting symbols may also be configured by using a field newly defined for the configuring the number of shifting symbols in the DCI or a conventional field (e.g., the TCI state field, the antenna port(s) field, the MCS field, the NDI field, the RV field, etc.). As an example, the repeated transmission number may be replaced with the number of shifting symbols and interpreted in the method and/or embodiment (e.g., examples 1 to 5).

<Proposal 2-2>

The method and/or embodiment (e.g., examples 1 to 5) may also be used as a method for indicating different RV values of different transmission occasions in the case of scheme 2b/3.

In the case of scheme 2b/3, in respect to different RV values of different transmission occasions, a value of a first RV field indicated to the UE may indicate an RV value of the first transmission occasion, and in respect to the RV value of the second transmission occasion, a difference value and/or a value of actual RV and/or RV combination related indication information may be separately signaled based on the value indicated as the first RV field. The following method may become one example of a method for indicating the difference value of the RV value and/or the actual RV value and/or the RV combination related indication information.

Hereinafter, proposed is a method for indicating RV related information for each transmission occasion in time domain repetition transmission. For convenience of description, an example of the case where two TRPs (e.g., TRP 1 and TRP 2) perform coordinated transmission is primarily described, but does not limit the scope of the present disclosure. Accordingly, the method may be applied even to a case where three or more TRPs perform the coordinated transmission, of course. Further, a single DCI based M-TRP operation is assumed and described.

In the example of Proposal 2-2, it is assumed that the first transmission occasion corresponds to TRP 1 and the second transmission occasion corresponds to TRP 2. Here, the different transmission occasions may be interpreted as different (transmission) resource domains corresponding to different TRPs.

In respect to the method and/or embodiments (e.g., examples 1 to 5), different RV values may be indicated for the transmission resource regions corresponding to different TRPs. This is because independent encoded bits may correspond to respective transmission resource regions corresponding to different TRPs. When different RV values may be indicated to the independent encoded bits corresponding to different TRPs as such, there may be an advantage in that a most appropriate RV combination may be indicated according to a channel environment.

For example, when there is a path loss difference between different channels corresponding to different TRPs, more parity bits may be transmitted by indicating a combination of self decodable RV (e.g., 0 and/or 3) and non-self decodable RV (e.g., 1 and/or 2 and/or 3), and robust channel coding may be applied. On the contrary, when the path loss difference between different channels corresponding to different TRPs is large or a blockage environment is considered, the self decodable RV is mapped to all of the different TRPs to receive self decodable encoded bits even in one TRP among different TRPs, thereby enhancing a reception capability of the UE.

In the present disclosure, the ‘self decodable RV’ may mean a decodable RV value by receiving single encoded bits due to a low effective coding rate, and the ‘non-self decodable RV’ may mean an RV value which is difficult to decode by receiving the single encoded bits due to a high effective coding rate. In the present disclosure, the ‘blockage environment’ may mean a channel environment in which the reception SNR from the relevant TRP is very low because a channel from a specific TRP becomes weak. The ‘encoded bits’ mentioned in the present disclosure may also be referred to as codeword (CW).

The following method may be applied in order to indicate different RV values to respective encoded bits corresponding to the transmission resource regions corresponding to different TRPs. Hereinafter, a method for configuring the RV value corresponding to each transmission occasion will be described in detail.

Method 1: The RV value (e.g., a first RV value) may be indicated through the RV field of the DCI and a difference value from the RV value (e.g., the first RV value) may be indicated. Method 1 is a method for indicating an actual different value (e.g., alpha) compared with x when it is assumed that the RV value (e.g., the first RV value) indicated through the first RV field is x. For example, when X is indicated by the RV value based on the first RV field and the alpha is indicated, the RV value of the second transmission occasion may be determined as X+alpha. For example, when it is assumed that the x is 0, if the difference value indicates 3, the RV value of the first transmission occasion corresponds to 0 and the RV value of the second transmission occasion corresponds to 3.

Method 2: A method for indicating a difference value in the relevant order after defining a specific RV order may be considered. For Method 2, first, multiple RV values need to be defined in a specific order. To this end, the RV order used for retransmission may be used. For example, the order of the RV values may be defined in the order of 0, 2, 3, and 1. In addition, when the RV value indicated through the first RV field is x, what numberth RV value the relevant RV value is may be cyclically indicated based on x. For example, when 0 is indicated as the RV value of the first transmission occasion and 3 is indicated as the difference value, the RV value of the second transmission occasion corresponds to 1 positioned in an order behind 0 by three steps.

Method 3: Multiple RV values (e.g., the first RV value and the second RV value) may be indicated through the RV field of the DCI. That is, another RV value (e.g., the second RV value) to be actually applied may be indicated according to Method 3 in addition to the RV value (e.g., the first RV value) indicated through the first RV field.

Method 4: Method for Indicating RV Combination

A method for indicating different RV values to the transmission resource regions corresponding to different TRPs may be considered. That is, a method for indicating the RV combination for different transmissions occasions (e.g., the first transmission occasion/the second transmission occasion) may also be considered. Here, the different transmission occasions may be interpreted as different (transmission) resource domains corresponding to different TRPs.

An RV value for the encoded bits transmitted through a specific (transmission) resource region corresponding to a specific TRP among multiple TRPs, and an RV value for encoded bits transmitted through a specific resource region corresponding to other TRPs other than the specific TRP may be fixed/configured (e.g., RRC signaling and/or MAC-CE signaling) to a specific value (i.e., default value, e.g., 0).

For example, when two TRPs are configured, an RV value for one TRP (e.g., TRP 1) may be dynamically indicated through the RV field in the DCi, and an RV value for the other TRP (e.g., TRP 2) other than the relevant TRP may be fixed to a specific value or configured through the higher layer signaling. Further, for example, when three or more TRPs are configured, an RV value for one TRP among multiple TRPs may be dynamically indicated through the RV field in the DCI, and an RV value for a TRP(s) other than the one specific TRP may be fixed to a specific value (s) or configured through the higher layer signaling. In this case, the specific value (s) may be fixed/configured to the same value for all TRP(s), or fixed/configured to an individual value for each TRP(s).

As an example, in the proposal, the ‘specific resource region corresponding to the specific TRP’ may be a resource region corresponding a first TCI state (e.g., TCI state #0) and/or CW #0 and/or a first TB field. The ‘first’ may become one example, and may be replaced with another specific value such as second, etc. That is, the specific resource region corresponding to the specific TRP may be a resource region corresponding to a specific TCI state, a specific CW, and/or a specific TB field. The relevant specific value may be fixed as a (pre)-static value between the BS and the UE or the BS may also configure, to the UE, the relevant specific value through the higher layer signaling (e.g., RRC/MAC-CE) and/or DCI signaling. When the proposal is applied, an example of an RV combination which may be indicated to each of TRPs 1 and 2, i.e., corresponds to the encoded bits corresponding to the resource region corresponding to each TRP may be shown in Table 16.

Table 16 shows an example of an RV combination corresponding to each TRP. In the example of Table 16, the RV value of TRP 2 may be fixed/configured to 0 or another value (e.g., 1/2/3). As an example, the another value may be configured through the higher layer signaling.

TABLE 16 RV value indicated TRP 1 (e.g., for TRP 2 (e.g., for the by RV field in DCI the first TCI state) second TCI state) 0 0 0 or higher layer signaled value 1 1 0 or higher layer signaled value 2 2 0 or higher layer signaled value 3 3 0 or higher layer signaled value

When Method 4 described is applied, the following advantage may be obtained. First, different RV combinations for different TRPs may be indicated through a single specific RV field in the DCI. Second, a specific TRP among different TRPs may continuously transmit the encoded bits of the self decodable RV. As an example, when Method 4 above is applied, in the case of an environment in which the path loss difference between different channels corresponding to different TRPs is small, a combination of the self decodable RV and the non-self decodable RV may be indicated. On the contrary, in the case of an environment in which the path loss difference is large or blockage may occur, the combination of the self decodable RV and the self decodable RV may be indicated. Through this, there is a technical effect capable of dynamically indicating a robust (i.e., optimized) RV combination according to a channel environment.

Further, jointly with Method 4 described above, a method for indicating the RV combination constituted by multiple RV values through the RV field in the DCI may also be considered. When such a method is applied, there may be a feature that the RV field may correspond to multiple RV values differently from a case where the RV field corresponds to a specific RV value in a conventional standard.

Table 17 illustrates an example in which a combination of multiple RV values is indicated/configured. Table 17 is just an example for convenience of the description and does not limit the technical scope of the present disclosure.

TABLE 17 RV value indicated TRP 1 (e.g., for TRP 2 (e.g., for the by RV field in DCI the first TCI state) second TCI state) 0 0 0 1 0 3 2 0 2 3 1 3

Referring to Table 17, the RV value (or index) may be indicted through the RV field in the DCI, and multiple RV values may be mapped for each RV value. In other words, a mapping relationship of multiple RV values may be pre-defined for each codepoint of the RV field of the DCI, and the RV value corresponding to each TRP may determined based on a value indicated by the DCI.

As in the example of Table 17, when the method for indicating the RV combination constituted by multiple RV values is applied, there may be a feature that the value indicted through the RV field is different from the RV value to be actually applied. The RV combination corresponding to each RV field may be defined as a static value between the BS and the UE, and a specific RV combination may be configured to the UE through the higher layer signaling and/or the DCI signaling.

Method 5: Method for Indicating Mapping Relationship Between RV Combination and TRP

According to Method 4 described above, there may be an advantage in that different RV values may be indicated to different encoded bits corresponding to different TRPs. The ‘different encoded bits corresponding to different TRPs’ may be interpreted as different encoded bits corresponding to different TCI states. Meanwhile, Method 4 above has a feature that the RV combination indicated through the specific RV field is fixed in a specific order. For example, according to Method 4, 3 may be indicated to encoded bits corresponding to the first TRP through the RV field in the DCI and 0 may be indicated to encoded bits corresponding to the second TRP, but contrary to this, 0 and 3 may not be indicated.

The limitation may have a disadvantage in that when the BS indicates the RV order differently according to the channel state between the TRP and the UE, the combination of the TCI states is the same, but respective codepoints having a different order should be defined in the TCI state field, and as a result, efficiency of the TCI state field deteriorates. For example, when each of codepoint 0 corresponding to {TCI state A, TCI state B} of the TCI field and codepoint 1 corresponding to {TCI state B, TCI state A} is defined, combinations of {2, 0} and {0, 2} may be indicated to encoded bits corresponding to TCI state A and encoded bits corresponding to TCI state B through codepoint 0 and codepoint 1, respectively (in Method 4, it is assumed that 2 is indicated in the RV field).

A method capable of changing an order (or the order o the TCI state) of TRPs corresponding to different RVs may be considered in order to overcome the disadvantage.

Method 5-1) Specific mapping order related information may be indicated based on the index of the CDM group including the DMRS port(s) indicated through the antenna port(s) field in the DCI (e.g., see an antenna port related table of DCI format 1-1 described in section 4.1.7). That is, different mapping orders may be indicated according to the index of the CDM group. As an example, when the indicated CDM group index is 0, i.e., when the indicated DMRS port(s) is included in CDM group 0, the first RV value in the RV combination (e.g., the RV combination configured by the BS as in Method 4) indicated to the UE may be applied to the encoded bits corresponding to the first TCI state and the second RV value may be applied to the encoded bits corresponding to the second TCI state. On the contrary, when the indicated CDM group index is 1, i.e., when the indicated DMRS port(s) is included in CDM group 1, the first RV value in the RV combination indicated to the UE may be applied to the encoded bits corresponding to the second TCI state and the second RV value may be applied to the encoded bits corresponding to the first TCI state. Alternatively, the opposite case is also possible.

Method 5-2) A Modulation and Coding Scheme (MCS)/New Data Indicator (NDI) field for a second transport block (TB) of the DCI may be used. For example, different mapping orders may be indicated through 1 bit of the MCS/NDI field

Method 5-3) Specific mapping order related information may be indicated based on the DMRS antenna port(s) index through the antenna port(s) field in the DCI.

For example, the specific mapping order related information may be mapped to a specific DRMS antenna port or DMRS antenna ports (DMRS antenna port group).

Table 18 shows an example of mapping specific mapping order related information to a specific DMRS antenna port and Table 19 shows an example of mapping the specific mapping order related information to a specific DMRS antenna port group. The DMRS antenna port group may be constituted by multiple DMRS antenna ports.

TABLE 18 Type 1 Type 2 Mapping order Mapping order between TCI states between TCI states DMRS port and RV values DMRS port and RV values 0 k1 0 k1  1 k2 1 k2  2 k3 2 k3  3 k4 3 k4  4 k5 4 k5  5 k6 5 k6  6 k7 6 k7  7 k8 7 k8  8 k9  9 k10 10 k11 11 k12

TABLE 19 Type 1 Type 2 Mapping order Mapping order between TCI states between TCI states DMRS port and RV values DMRS port and RV values 0 k1 0 k1 1 k1 1 k1 2 k2 2 k2 3 k2 3 k2 4 k3 4 k3 5 k3 5 k3 6 k4 6 k4 7 k4 7 k4 8 k5 9 k5 10 k6 11 k6

In the examples of Table 18 and Table 19, k1 to k12 may mean different mapping order related information. In this case, some of the values of k1 to k12 may correspond to the same mapping order. The mapping order corresponding to k1 to k12 above may be configured to the UE through the higher layer signaling or a specific mapping order may be defined by a static rule between the BS and the UE.

Referring to Table 18, different mapping order related information may be mapped to different DMRS antenna ports. Further, referring to Table 19, different mapping order related information may be mapped by a group granularity constituted by multiple DMRS antenna ports. In the examples of Table 18 and Table 19, different mapping order related information may be indicated according to the DMRS port index indicated to the UE. For example, when Table 19 is assumed, when DMRS port 0 is indicated to the UE, the mapping order related information (e.g., the first RV is mapped to the first TCI state and the second RV is mapped to the second TCI state) corresponding to k1 may be indicated and when DRMS port 2 is indicated, the mapping order related information (e.g., the second RV is mapped to the first TCI state and the first RV is mapped to the second TCI state) corresponding to k2 may be indicated.

Meanwhile, when multiple DMRS ports are indicated to the UE, the UE may assume mapping order related information corresponding to a specific DRMS port. For example, mapping order related information corresponding to a higher or lower index may be defined to be followed. As an example, when DMRS ports 0 and 1 are indicated, and defined to correspond to the lower index, the mapping order related information corresponding to k1 corresponding to DMRS port 0 may be indicated.

Further, different mapping order information may also be indicated according to the DMRS port index in the same CDM group. In other words, specific mapping order related information may be mapped to a DMRS antenna port group constituted by the DMRS antenna ports included in different CDM groups.

Table 20 shows an example of indicating different mapping order related information according to the order of the DMRS port index by a CDM group granularity.

TABLE 20 Type 1 Type 2 Mapping order Mapping order CDM between TCI CDM between TCI group DMRS states and group DMRS states and index port RV values index port RV values 0 0 k1 0 0 k1 1 k2 1 k2 4 k3 6 k3 5 k4 7 k4 1 2 k1 1 2 k1 3 k2 3 k2 6 k3 8 k3 7 k4 9 k4 2 4 k1 5 k2 10 k3 11 k4

In the example of Table 20, k1 to k4 mean different mapping order related information. In this case, some of the values of k1 to k4 may correspond to the same mapping order. The mapping order related information may be configured to the UE through the higher layer signaling or a specific mapping order may be defined by a static rule between the BS and the UE.

Referring to Table 20, the different mapping order related information may be mapped according to the DMRS port index in the same CDM group. In other words, the different mapping order related information may be indicated according to the order in the CDM group including the relevant DMRS ports based on the DMRS port index indicated to the UE. For example, when DMRS configuration type 1 is assumed, in a case where DMRS port 0 is indicated to the UE, mapping order related information corresponding to k1 may be indicated and in a case where DMRS port 4 is indicated, mapping order related information corresponding to k3 may be indicated.

Meanwhile, when multiple DMRS ports are indicated to the UE, the UE may assume mapping order related information corresponding to a specific DRMS port. For example, mapping order related information corresponding to a higher or lower index may be defined to be followed. As an example, when DMRS ports 0 and 1 are indicated, and defined to correspond to the lower index, the mapping order related information corresponding to k1 corresponding to DMRS port 0 may be indicated.

Method 6:

In Method 5 and Method 5-1/5-2/5-3, proposed is a method capable of indicating different mapping orders for a TCI state combination constituted by multiple TCI states defined in a specific codepoint of the TCI state field in the DCI and an RV combination indicated through the RV field. For example, when {TCI state A, TCI state B} is indicated through the specific codepoint of the TCI state field and {RV0, RV2} is indicated through the RV field, a mapping relationship between {TCI state A-RV0, TCI state B-RV2} or {TCI state A-RV2, TCI state B-RV0} may be determined through the CDM group index. That is, in this case, in order to apply different mapping orders between TCI states and RV values, additional information (e.g., CDM group index, DMRS port index, etc.) may be required.

Unlike this, a method for defining an RV combination constituted by the same RC values and having different orders in the RV field may be applied in addition to the proposed scheme. That is, a combination autonomously having different mapping orders between the TCI states and the RV values in the RV field may be configured/defined. In addition, it is apparent that even when schemes of Method 5 and Method 5-1/5-2/5-3 described above are not applied, the relevant method may be applied as a method for indicating different RVs in resource regions corresponding to different TCI states.

Table 21 shows an example of a method for indicating the RV combination according to Method 6 of the present disclosure.

TABLE 21 Value of the Value of rvid to be Value of rvid to be redundancy version applied to transmission applied to transmission field (order may be occasion with the first occasion with the second changed) (or second) TCI state (or first) TCI state 00 0 0 01 0 2 10 2 0 11 1 3

In the example of the RV combination, RV combinations corresponding to 01 and 10 which are values of the RV field are {0, 2} and {2, 0}, respectively. As an example, an RV combination of {x, 0} and {0, x} (e.g., x=one value of {1, 2, 3}) in the RV field may be defined/configured. The combination has a feature that the combination is constituted by the same RV values and has different orders. When the RV combinations having the feature are jointly defined in the RV field, the BS has an advantage of being capable of indicating RV combinations of different orders through the RV field according to channel situations of different TRPs. That is, the BS has an advantage of being capable of configuring and/or indicating an optimized RV combination by determining and considering the channel situation of each TRP. For example, when TRP A has a better channel (e.g., higher CQI) in respect to TRP A/B (e.g., TRP A is mapped to the first TCI state and TRP 2 is mapped to the second TCI state), RV0 which is self-decodable RV may be indicated for TRP A and RV2 may be indicated for TRP B.

There may be an RV combination of Table 22 as another example having the same purpose.

TABLE 22 Value of the Value of rvid to be Value of rvid to be redundancy version applied to transmission applied to transmission field (order may be occasion with the first occasion with the second changed) (or second) TCI state (or first) TCI state 00 0 0 01 0 2 10 3 0 11 1 3

In the example of the RV combination, RV combinations corresponding to 01 and 10 which are values of the RV field are {0, 2} and {3, 0}, respectively. As an example, an RV combination of {x, 0} and {0, y} (e.g., x=one value of {1, 2, 3} and y=one value of [1, 2, 3] other than the x) in the RV field may be defined/configured. A difference from the previous RV combination is that an RV combination corresponding to 10 is not {2, 0} but {3, 0}. The example may have an advantage of being capable of changing the order of the TRP in which RV0 which is the self-decodable RV is mapped and an advantage of being capable of defining more various RV combinations.

Another example of the RV combination suitable for applying the schemes of Method 5 and Method 5-1/5-2/5-3 in addition to the proposal is shown in Table 23.

TABLE 23 Value of the Value of rvid to be Value of rvid to be redundancy version applied to transmission applied to transmission field (order may be occasion with the first occasion with the second changed) (or second) TCI state (or first) TCI state 00 0 0 01 2 (or 1 or 3) 2 (or 1 or 3) 10 0 2 11 1 (or 3) 3 (or 1)

A reason why the RV combination is suitable is as follows. First, the RV combination may be defined by considering a blockage environment in which large path loss may occur radically and a non-blockage environment in which the blockage may not be considered. Accordingly, the (0, 0) combination should be defined to receive the self-decodable RV (e.g., RV0) from a TRP in which the blockage does not occur even when the blockage occurs by considering the blockage environment. Meanwhile, the (0, 2) combination should be defined by considering the non-blockage environment. The reason is that it is anticipated that the (0, 2) combination may have a lower effective channel coding rate due to increment redundancy to have an excellent capability in most environments. The reason why RV combinations (2, 2) and (1, 3) should be defined based on the RV combinations is that retransmission is considered. In the case of the (0, 0) combination, RV0 and RV2 are received through the TRP in which the blockage does not occur even though the blockage occurs in a specific TRP of two TRPs to reduce the effective channel coding rate through the (2, 2) combination upon retransmission Although it is assumed that (RV0, RV0) and (RV2, RV2) are defined by applying RV0 and RV2 in the example, RV2 may be replaced with RV1 or RV3 in the example, and even in this case, a similar feature and a similar effect may be obtained (e.g., (2, 2) may be (1, 1) or (3, 3) in Table 23 above).

Meanwhile, in the case of the (0, 2) combination considering the non-blockage environment, the UE may receive data for all RVs and lower the effective channel coding rate as possible through the (1, 3) combination upon retransmission. The order of RV1 and RV3 is applied in the example, and it is also possible to define an order of being mapped to different TCI state as an order of RV3 and RV1. Further, the (0, 2) combination considering the non-blockage environment may be replaced with a combination of (0, x) and defined, and in this case, the RV combination for retransmission in the non-blockage environment may be defined as (y, z) value other than the (0, x). In the example, x may become one value of 1, 2, and 3, and y and z may correspond to values which are not redundant, respectively among values other than 0 and x. For example, when a combination indicated by Value “10” is (0, 1), a combination indicated by Value “11” may be (2, 3) or (3, 2). Alternatively, for example, when the combination indicated by Value “10” is (0, 3), the combination indicated by Value “11” may be (1, 2) or (2, 1).

The example of the specific RV combination may be an example, and it is apparent that it is possible to apply the feature of the proposed scheme to RV combinations constituted by using other RV values.

Further, in the present disclosure an RV value, RV value information, or RV value related information or RV value indication information may be interpreted/used as an actual RV difference value/a difference value in the order/an actual RV value/RV combination related indication information.

<Proposal 2-3>

In Proposal 2-1 described above, the method for indicating the number of shifting symbols between different transmission occasions is described. Further, in Proposal 2-2 described above, the method for indicating different RV values of different transmission occasions is described. The method and/or embodiment (e.g., examples 1 to 5) of Proposal 2 described above may be used in order to indicate the number of shifting symbols and/or the RV value related information (e.g., the difference value of the RV value, the actual RV value, the RV combination related indication information, etc.).

The BS may configure values applicable to the number of shifting symbols and/or the RV value related information to the UE through the higher layer signaling (e.g., RRC/MAC CE). And/or, a candidate value(s) for the number of shifting symbols and/or the RV value related information which are fixed and/or (pre)-promised between the BS and the UE may be defined, and the BS may implicitly or explicitly indicate a specific value among the candidate value(s) for the number of shifting symbols and/or the RV value related information which may be indicated to the UE through a specific field in the DCI.

In the proposal, the candidate value may mean some/all values which the BS configures to the UE through the higher layer signaling based on a pre-configured/defined promise/rule/condition among the number of shifting symbols and/or the RV value related information. Further, the specific field in the DCI may be a field newly defined for indicating the number of shifting symbols and/or the RV value related information or a conventional field (e.g., the TCI state field, the antenna port(s) field, the MCS field, the NDI field, the RV field, etc.).

For example, when the number of shifting symbols and/or the RV value related information are/is configured to the UE through the higher layer signaling, it may be assumed that {1, 2, 3, 4} are defined as the number applicable of shifting symbols. Some (e.g., {1, 2}) of the values as the number of shifting symbols and/or the RV value related information may be configured to the UE through the higher layer signaling. For example, a specific value of the candidate value(s) (e.g., {1, 2}) may be indicated through the specific field in the DCI.

For example, as an example of the specific field in the DCI, the antenna pots) field may be used. A specific shifting symbol number and/or RV value related information may be indicated based on the index of the CDM group indicated through the antenna port(s) field. As an example, when the indicated CDM group index is 0 (i.e., when the indicated DMRS pots) is included in CDM group 0), a smaller shifting symbol number among the candidate values for the shifting symbol number and/or smaller RV value related information among the candidate values for the RV value related information may be indicated. When the indicated CDM group index is 1 (i.e., when the indicated DMRS port(s) is included in CDM group 1), a larger shifting symbol number among the candidate values for the shifting symbol number and/or larger RV value related information among the candidate values for the RV value related information may be indicated.

As a specific example, when the candidate value for the shifting symbol number such as {1, 2} is configured, 1 shift symbol may be indicated in the case of indicating CDM group index 0 and 2 shifting symbols may be indicated in the case of indicating CDM group index 1. Alternatively, the opposite case is also possible.

As another example, a Modulation and Coding Scheme (MCS)/New Data Indicator (NDI)/Redundancy Version (RV) field for a second transport block (TB) in the DCI may be used. For example, different shifting symbol numbers and/or RV value related information may be mapped to a codepoint corresponding to the MCS/NDI/RV field for the second TB, and the BS may indicate, to the UE, a specific shifting symbol number and/or RV value related information through the relevant field.

As another example, as an example of the specific field in the DCI, the antenna port(s) field may be used. For example, a specific shifting symbol number and/or RV value related information may be indicated based on the DMRS antenna port(s) index indicated through the antenna port(s) field.

As an example, the specific shifting symbol number and/or RV value related information may be mapped to specific DRMS antenna ports or DMRS antenna ports (DMRS antenna port group).

Table 24 shows an example in which different shifting symbol numbers and/or RV value related information are mapped to different DMRS antenna ports. Table 25 shows an example in which different shifting symbol numbers and/or RV value related information are mapped by a group granularity constituted by multiple DMRS antenna ports.

TABLE 24 Type 1 Type 2 the number of the number of shifting symbols shifting symbols DMRS port and/or RV value DMRS port and/or RV value 0 k1 0 k1  1 k2 1 k2  2 k3 2 k3  3 k4 3 k4  4 k5 4 k5  5 k6 5 k6  6 k7 6 k7  7 k8 7 k8  8 k9  9 k10 10 k11 11 k12

TABLE 25 Type 1 Type 2 the number the number DMRS port of repetition DMRS port of repetition 0 k1 0 k1 1 k1 1 k1 2 k2 2 k2 3 k2 3 k2 4 k3 4 k3 5 k3 5 k3 6 k4 6 k4 7 k4 7 k4 8 k5 9 k5 10 k6 11 k6

In Tables 24 and Table 25, k1 to k12 may mean different shifting symbol numbers and/or RV value related information. In this case, some of the values of k1 to k12 may correspond to the same value. The values corresponding to k1 to k12 above may be configured to the UE through the higher layer signaling or specific values may be defined by a static rule between the BS and the UE.

In the examples of Table 24 and Table 25, different shifting symbol numbers and/or RV value related information may be indicated according to the DMRS port index indicated to the UE. For example, referring to Table 25, when DMRS port 0 is indicated to the UE, the shifting symbol number and/or RV value related information corresponding to k1 may be indicated and when DMRS port 2 is indicated, the shifting symbol number and/or RV value related information corresponding to k2 may be indicated.

Meanwhile, when multiple DMRS ports are indicated to the UE, the UE may assume a shifting symbol number and/or RV value related information corresponding to a specific DRMS port. For example, a shifting symbol number and/or RV value related information corresponding to a higher or lower index may be defined to be followed. As an example, when DMRS ports 0 and 1 are indicated, and defined to correspond to the lower index, the shifting symbol number and/or RV value related information corresponding to k1 corresponding to DMRS port 0 may be indicated.

In addition to the proposal, a method for indicating different shifting symbol numbers and/or RV value related information may be indicated according to the order of the DMRX port index in the same CDM group. In other words, a specific shifting symbol number and/or RV value related information may be mapped to a DMRS antenna port group constituted by the DMRS antenna ports included in different CDM groups.

Table 26 shows an example of mapping different shifting symbol numbers and/or RV value related information according to the order of the DMRS port index in the same CDM group.

TABLE 26 Type 1 Type 2 the number the number of shifting of shifting CDM symbols CDM symbols group DMRS and/or RV group DMRS and/or RV index port value index port value 0 0 k1 0 0 k1 1 k2 1 k2 4 k3 6 k3 5 k4 7 k4 1 2 k1 1 2 k1 3 k2 3 k2 6 k3 8 k3 7 k4 9 k4 2 4 k1 5 k2 10 k3 11 k4

In Table 26, k1 to k4 mean different shifting symbol numbers and/or RV value related information. In this case, some of the values of k1 to k4 may correspond to the same value. The shifting symbol number and/or RV value related information may be configured to the UE through the higher layer signaling or a specific value may be defined by a static rule between the BS and the UE.

Referring to Table 26, different shifting symbol numbers and/or RV value related information may be indicated according to the order in the CDM group including the relevant DMRS ports based on the DMRS port index indicated to the UE. For example, in the case of assuming DRMS configuration type 1, when DMRS port 0 is indicated to the UE, the shifting symbol number and/or RV value related information corresponding to k1 may be indicated and when DMRS port 4 is indicated, the shifting symbol number and/or RV value related information corresponding to may be indicated.

Meanwhile, when multiple DMRS ports are indicated to the UE, the UE may assume a shifting symbol number and/or RV value related information corresponding to a specific DRMS port. For example, a shifting symbol number and/or RV value related information corresponding to a higher or lower index may be defined to be followed. As an example, when DMRS ports 0 and 1 are indicated, and defined to follow the shifting symbol number and/or RV value related information corresponding to the lower index, the shifting symbol number and/or RV value related information corresponding to k1 corresponding to DMRS port 0 may be indicated.

As in the example of Table 26, when different shifting symbol numbers and/or RV value related information are indicated according to the order of the DMRX port index in the same CDM group, there may be the following advantage.

When a situation of multi-user (MU)-pairing assuming scheme 2b or scheme 3 is considered, it is more natural that a small number of UEs are MU-paired than a large number of UEs are MU-paired. The reason is that MU-pairing is primarily used for a purpose of increasing a data transmission rate by simultaneously transmitting data to multiple UEs, and to this end, precoding orthogonal to different UEs should be able to be applied so as to prevent interference between UEs. However, in the case of URLLC, it is preferable to minimize interference with another UE and further, in order to reduce a latency time, urgent data transmission may be performed, and in this case, it may be difficult and not preferred to find a UE having precoding orthogonal for a short time. Accordingly, when it is assumed that a small number of UEs are MU-paired, different UEs may be supported through the DMRS port(s) included in different CDM groups. The reason is that it is anticipated that interference between DMRS ports which are multiplexed based on FDM upon channel estimation is smaller than interference between DMRS ports which are multiplexed based on CDM.

When a situation is assumed in which different UEs are supported through DMRS port(s) included in different CDM groups, different shifting symbol numbers and/or RV value related information should be able to be indicated to the respective UEs through the DMRS port(s) in the same CDM group.

For example, when the maximum number of symbols of the DMRS is 1 and DMRS type 1 is assumed, DMRS ports 0 and 1 and DMRS ports 2 and 3 are included in CDM groups 0 and 1, respectively. In this case, when DMRS ports 0 and 1 correspond to the same shifting symbol number and/or RV value related information and DRMS ports 2 and 3 correspond to the same shifting symbol number and/or RV value related information, there is no method capable of indicating different shifting symbol numbers and/or RV value related information to different respective UEs. Accordingly, it may be regarded that it is preferable that different shifting symbol numbers and/or RV value related information correspond to different DMRS port(s) in the same CDM group.

To this end, according to the proposed method, different shifting symbol numbers and/or RV value related information may be mapped according to the order of the DMRS port index in the same CDM group, and a specific shifting symbol number and/or RV value related information may be indicated according to the DMRS port index indicated to the UE.

Table 27 shows another example of mapping different shifting symbol numbers and/or RV value related information according to the order of the DMRS port index.

TABLE 27 Type 1 Type 2 the the number of number of shifting shifting CDM symbols CDM symbols group DMRS and/or RV group DMRS and/or RV index port value index port value 0 0 k1 0 0 k1 1 k2 1 k2 4 k3 6 k3 5 k4 7 k4 1 2 k2 1 2 k2 3 k1 3 k1 6 k4 8 k4 7 k3 9 k3 2 4 k1 5 k2 10 k3 11 k4

Table 27 has a feature in that Table 27 is different from Table 26 in terms of shifting symbol numbers and/or RV value related information corresponding to DMRS ports included in CDM group 1. This has a feature in that when multiple DMRS ports are indicated to the UE, in a case where a shifting symbol number and/or RV value related information corresponding a small or large DRMS port is defined to be followed, different shifting symbol numbers and/or RV value related information may be indicated through DMRS port combinations included in different CDM groups.

As an example, when Table 26 and the shifting symbol number and/or RV value related information corresponding to the small DMRS port, the shifting symbol number and/or RV value related information corresponding to k1 may be indicted for each of the combination of DMRS ports 0 and 1 and the combination of DMRS ports 2 and 3. On the contrary, when Table 27 is assumed, the shifting symbol number and/or RV value related information corresponding to k1 for DRMS ports 0 and 1 and k2 for DMRS ports 2 and 3 may be indicated.

Meanwhile, in addition to matters presented in the examples of Tables 24, 25, 26, and 27, the shifting symbol number and/or RV value related information corresponding to each DMRS port may be defined differently according to the maximum symbol number (e.g., ‘maxLength’) of the DMRS configured to the UE.

Table 28 shows an example of differently defining the shifting symbol number and/or RV value related information corresponding to each DMRS port according to the maximum symbol number of the DMRS based on Table 27.

TABLE 28 Type 1 Type 2 the number the number of shifting of shifting CDM symbols CDM symbols group DMRS and/or RV group DMRS and/or RV index port value index port value maxLength = 1 0 0 k1 0 0 k1 1 k2 1 k2 1 2 k2 1 2 k2 3 k1 3 k1 2 4 k1 5 k2 maxLength = 2 0 0 k1 0 0 k1 1 k3 1 k3 4 k2 6 k2 5 k4 7 k4 1 2 k1 1 2 k1 3 k3 3 k3 6 k2 8 k2 7 k4 9 k4 2 4 k1 5 k3 10 k2 11 k4

Referring to Table 28, the shifting symbol number and/or RV value related information corresponding to the DMRS port may be differently defined according to the maximum symbol number of the DMRS. For example, when the maximum symbol number is 1 (i.e., maxLength=1), the shifting symbol numbers and/or RV value related information corresponding to k1 and k2, respectively may be indicated b using DMRS ports within different CDM group in the case of 1 layer transmission. Further, in the case of 2 layer transmission, when it is assumed that a repeated transmission number corresponding to the small DMRS port is followed, k1 and k2 may be indicated by using the (0, 1) combination and the (2, 3) combination, respectively. On the contrary, in the case where the maximum symbol number is 2 (i.e., maxLength=2), the shifting symbol numbers and/or RV value related information corresponding to k1, k2, k3, and k4 may be indicated by using DMRS ports in different CDM groups, respectively in the case of the 1 layer transmission, and k1 and k2 may be indicated by using the (0, 1) combination and the (4, 5) combination, respectively by assuming that the repeated transmission number corresponding to the small DMRS port is followed, and k1 and k2 may be indicated by using the (2, 3) combination and the (6, 7) combination, respectively in the case of the 2 layer transmission.

That is, in the example, there is a feature that in the case where the maximum symbol number of the DMRS is 1, different shifting symbols numbers and/or RV value related information may be indicated through the DMRS port combination in different CDM groups upon the 2 layer transmission, and in the case where the maximum symbol number is 2, different shifting symbols numbers and/or RV value related information may be indicated through the DMRS port combination in the same CDM group upon the 2 layer transmission.

Table 27 may have an advantage in that since the shifting symbols numbers and/or RV value related information corresponding to k1, k2, k3, and k4 may be indicated upon the 2 layer transmission, more various shifting symbol numbers and/or RV value related information may be indicated by assuming one UE.

Table 28 may have an advantage in that since the shifting symbol numbers and/or RV value related information corresponding to k1 and k2 may be indicated, but the same shifting symbol number and/or RV value related information may be indicated within each of different CDM groups, upon the 2 layer transmission, independent shifting symbol numbers and/or RV value related information may be indicated to different UEs when considering the MU-pairing.

<Proposal 3>

Proposal 3 in the present disclosure proposes a method for configuring/indicating a transmission resource region in repeated transmission in the time domain.

DCI (e.g., DCI format 1_1, etc.) includes one field, i.e., a ‘Time domain resource assignment’ for time domain resource scheduling. Accordingly, when the repeated transmission is intended to be performed in the time domain, a method capable of configuring a time resource for each transmission occasion is required. To this end, a new field may also be defined in the DCI, but in this case, a size of a DCI format is diversified, and as a result, complexity of the UE for decoding the PDCCH may increase. In order to configure/indicate a time domain resource for time domain repeated transmission while maintaining a conventional DCI format as it is, a specific rule may be defined between the BS and the UE.

When mini-slot granularity repeated transmission is configured/indicated to the UE, the time domain resource indicated through the DCI may correspond to the first transmission occasion and a time domain resource for the other transmission occasion may have the same size as the resource indicated by the DCI and may be configured in concatenation with the relevant resource. In other words, the time domain resource indicated based on the ‘time domain resource assignment’ field of the DCI may correspond to the first transmissions occasion. The time domain resource for the second transmission occasion may have the same size as the time domain resource of the first transmission occasion, and may be configured in concatenation therewith. As an example, the first transmission occasion and the second transmission occasion may have the same symbol number.

In the above description, the ‘mini-slot’ may mean a scheduling structure having a granularity of 2, 4, 6, and 7 symbols which may be indicated by PDSCH mapping type B.

FIG. 13 illustrates an example of resource allocation for repeated transmission in a time domain proposed in the present disclosure. FIG. 13 is just one example for convenience of the description and does not limit the technical scope of the present disclosure.

Referring to FIG. 13, four symbols of #3 to #6 are indicated through the DCI, and this assumes that the symbols are assigned for the first transmission occasion. In addition, the time domain resources (i.e., four symbols) having the same size may be concatenated and assigned for the second transmission occasion according to the proposed method. In the example of FIG. 13, only up to the second transmission occasion is illustrated, but the proposed may be applied even when there is an additional transmission occasion. For example, a third transmission occasion may be defined according to the rule after the second transmission occasion, and the proposal is applied transmission occasions which may be additionally defined based on the above transmission occasion to assign the time domain resource.

In the case of assigning the time domain resource for the repeated transmission as in the method of Proposal 3, since a separate DCI field is not required, there is an advantage in that the conventional DCI format may be maintained. Further, since additional signaling for resource configuration is not required for each transmissions occasion, it is advantageous even in terms of the signaling overhead.

In Proposal 3, when different transmission occasions are concatenated, application of the gap symbol(s) may be considered. When different transmission occasions are concatenated according to a specific subcarrier spacing (SCS) value or a UE capability related to whether the UE being capable of shifting an FFT window, whether to apply the gap symbol(s) may be determined.

For example, when the SCS is large, different transmission occasions may be concatenated with N symbol gaps. In other words, the resource of the second transmission occasion may be assigned from a symbol separated from (after) the first transmission occasion by N symbol gaps. The reason is that a case where the SCS is large may mean FR2 meaning a higher frequency band, and in this case, an influence of inter-symbol interference may increase due to a difference in transmission time from different TRPs, and a situation may occur in which a switching delay for transmission and reception beams of the BS/UE should be considered.

Accordingly, the BS may configure/indicate, to the UE, whether to apply the gap symbol(s) and/or the number of gap symbols when concatenating different transmission occasions. For example, whether to apply the gap symbol(s) and/or the number of gap symbols may be forwarded through the higher layer signaling (e.g., RRC/MAC-CE). For example, whether to apply the gap symbol(s) or/and the number of gap symbols may be configured/indicated to the UE while mapping to a specific subcarrier spacing (SCS) value. The SCS may mean an SCS value configured to the UE for downlink data reception. The mapping relationship may be fixedly defined between the BS and the UE or configured to the UE through the higher layer signaling.

As another example, a UE that may dynamically move according to a UE capability for dynamically shifting the FFT window which may mean a granularity by which the UE acquires a sample value for a symbol subjected to OFDM may concatenate different transmission occasions without the gap symbol, and otherwise, concatenate different transmission occasions with the gap symbol(s).

In the example of FIG. 13 above, two transmission occasions are assumed, but two or more multiple transmission occasions may be indicated/configured. When the method of Proposal 3 described above is applied, there may be a case where the repeated transmission should be performed by exceeding one slot in some cases. In order to prevent such a case, when the repeated transmission is made by exceeding one slot, a transmission occasion which may be defined in a first slot may be repeatedly transmitted by a slot granularity.

FIG. 14 illustrates an example of slot unit repeated transmission based on a transmission occasion structure defined in a first slot in order to prevent repeated transmission by exceeding one slot. Referring to FIG. 14, four symbols of #3 to #6 are indicated through the DCI, and this assumes that the symbols are assigned for the first transmission occasion. In addition, FIG. 14 shows that the time domain resources (i.e., four symbols) having the same size may be concatenated and assigned for the second transmission occasion according to the proposal. Since up to the second transmissions occasion may be transmitted in one slot, the second transmission occasion may be configured to be concatenated. In order to concatenate and configure the third transmission occasion, four symbols are required, but a remaining symbol exceeds one slot subsequent to three (11, 12, and 13). In this case, as proposed in the present disclosure, the transmission occasion structure which may be defined in the first slot may be repeatedly transmitted by the slot granularity.

In addition to Proposal 3 described above, a method for configuring the time domain resource for the transmission occasion for the repeated transmission even when time domain resources for different transmission occasions may not be assigned to the same slot may be required. Hereinafter, a method for solving such a problem will be described in detail.

As a first method, the BS may configure/indicate mini-slot granularity repeated transmission only in one slot so as to prevent such a problem from occurring. As described above, the ‘mini-slot granularity repeated transmission’ may mean a scheduling structure having repeated transmission by a granularity of 2, 4, 6, and 7 symbols which may be indicated by PDSCH mapping type B. In this case, time resources for all transmission occasions may be assigned in one slot, and the UE may not expect that the repeated transmission exceeding one slot is indicated.

As a second method, when the time domain resource for each transmission occasion is defined according to Proposal 3 above, if a transmission occasion exceeding a boundary of the slot is generated, the relevant transmission occasion may be defined to be assigned with a resource of the same form as the previous transmission occasion in a next slot.

FIG. 15 illustrates an example of resource allocation to a transmission occasion exceeding a slot boundary according to a method proposed in the present disclosure. FIG. 15 is just for convenience of the description and does not limit the technical scope of the present disclosure.

In the example of FIG. 15, it is assumed that the time domain resource indicated through the DCI is from symbol #8 to symbol #11, and the relevant resource is assigned to the first transmission occasion. When the method of Proposal 3 described above is considered, in the subsequent transmitted second transmission occasion, resources having the same size should be assigned in concatenation with each other after the first transmission occasion, but exceed the boundary of the slot in the example of FIG. 15. Accordingly, in this case, it may be assumed that in respect to the time domain resource for the second transmission occasion, a resource at the same location as the first transmission occasion is assigned in the next slot. That is, the resource for the second transmission occasion may be assigned from symbol #8 to symbol #11 of a second slot. Further, the same rule is applied even to the case of the third transmission occasion to assign resources of symbols #8 to #11 of a third slot.

When the resource is configured as such for the transmission occasion for the repeated transmission, the repeated transmission exceeding the slot boundary may be supported, but there may be a disadvantage in that the latency increases. As a method capable of supplementing such latency, a third method is proposed.

As a third method, when the time domain resource for each transmission occasion is defined according to Proposal 3 above, if a transmission occasion exceeding a boundary of the slot is generated, the relevant transmission occasion may be configured/defined to be transmitted from a specific symbol location of the next slot. For example, the specific symbol location may follow a front-load DMRS location for PDSCH mapping type A configured to the UE. The front-load DMRS location for PDSCH mapping type A may be configured to the UE through a higher layer parameter ‘dmrs-TypeA-Position’.

FIG. 16 illustrates an example of a time domain resource allocation method when a transmission occasion exceeding a slot boundary occurs to which the method proposed in the present disclosure may be applied. FIG. 16 is just one example for convenience of the description and does not limit the technical scope of the present disclosure.

Referring to FIG. 16, it is assumed that the time domain resource indicated through the DCI is from symbol #8 to symbol #11, and the relevant resource is assigned to the first transmission occasion. When the method of Proposal 3 described above is considered, in the subsequent transmitted second transmission occasion, resources having the same size should be assigned in concatenation with each other after the first transmission occasion, but exceed the boundary of the slot in the example of FIG. 16. Accordingly, in this case, it may be assumed that in respect to the time domain resource for the second transmission occasion, the resource is assigned from the front-load DMRS location for PDSCH mapping type A configured to the UE in the next slot. In FIG. 15, a case where ‘dmrs-TypeA-Position’ is configured to 2 is assumed.

In the example of FIG. 16, the third transmission occasion may be defined in the same slot according to Proposal 3 after the second transmission occasion, and resources having the same size may be assigned in concatenation with each other. In the proposal, there may be an advantage in that the latency may be reduced by removing an unnecessary delay.

In the proposal, it is proposed that ‘specific symbol location’ may more characteristically follow ‘front-load DMRS location for PDSCH mapping type A configured to UE, and when it is considered that PDCCH transmission from the BS may be achieved in a symbol duration earlier than the front-load DMRS location for PDSCH mapping type A configured to the UE, there may be an advantage in that a collision between the PDCCH and PDSCH which is repeatedly transmitted may be avoided through the proposed method.

As a fourth method, when the BS intends to perform the mini-slot granularity repeated transmission, the BS may configure/indicate a time resource assignment candidate for performing the mini-slot granularity repeated transmission. The BS may configure/indicate, to the UE, a specific time resource assignment scheme among the time resource assignment candidates while configuring/indicating the mini-slot granularity repeated transmission to the UE. The ‘mini-slot’ may mean a scheduling structure having a granularity of 2, 4, 6, and 7 symbols which may be indicated by PDSCH mapping type B.

The time resource assignment may be indicated to the UE through the ‘time domain resource assignment’ field in the DCI. According to the current standard, one time domain resource in one slot may be indicated through the field value. A method for enhancing a function of the ‘time domain resource assignment’ field in order to perform the mini-slot granularity repeated transmission may be considered as follows.

For example, in a case where the UE is configured/indicated with the mini-slot granularity repeated transmission and a case where the UE is not configured/indicated with the mini-slot granularity repeated transmission, an interpretation method of the field may be different.

Specifically, when the BS intends to perform the mini-slot granularity repeated transmission, the BS may configure/indicate a time resource assignment candidate corresponding to the field. For convenience of description, the candidate is referred to as a first candidate. Alternatively, when the relevant operation is not the mini-slot granularity repeated transmission, the BS may configure/indicate the time resource assignment candidate corresponding to the field. For convenience of description, the candidate is referred to as a second candidate.

When the UE is configured/indicated with the mini-slot granularity repeated transmission, the UE may expect that one of value of the first candidates will be indicated through the ‘time domain resource assignment’ field. On the contrary, when the operation is not the mini-slot granularity repeated transmission, the UE may expect that one value of the second candidates will be indicated. Additionally, time resource assignment candidates included in the first candidate may include time domain resource information for multiple transmission occasions. Further, the respective candidates may correspond to different transmission occasion numbers and a specific value is indicated to indicate a specific transmission occasion number.

In the proposed method, the BS may apply the method and/or embodiment of Proposal 1 described above in order to configure/indicate the mini-slot granularity repeated transmission to the UE. For example, the mini-slot granularity repeated transmission among multiple repeated transmission methods may be configured through the higher layer signaling, and whether the mini-slot granularity repeated transmission is actually performed may be indicated through the DCI. Accordingly, when it is indicated that the mini-slot granularity repeated transmission is actually performed through the DCI, one value of the first candidates may be indicated for the time resource assignment according to the proposed scheme, and when the mini-slot granularity repeated transmission is not indicated, one value of the second candidates may be indicated for the time resource assignment.

The example of the signaling may become one example for applying the proposed scheme, and it is apparent that other examples to which the proposed scheme is applied may also be included in the proposal, and a method to which a relevant proposed matter may be applied is not limited to the example.

Table 29 shows an example of first candidates which may be indicated through the ‘time domain resource assignment’ field when the mini-slot granularity repeated transmission is performed. Table 29 is just an example for helping to appreciate the present disclosure and does not limit the technical scope of the present disclosure.

TABLE 29 PDSCH Row mapping index type K0 S1 L1 S2 L2 S3 L3 S4 L4  1 Type B 0 5 2 7 2  2 Type B 0 5 2 7 2 9 2 11 2  3 Type B 0 9 2 11 2  4 Type B 0 4 4 8 4  5 Type B 0 6 4 10 4  6 Type B 0 0 7 7 7  7 Type B 0 5 2 7 4 11 2  8 Type B 0 4 2 6 2 8 4 12 2  9 Type B 0 5 2 8 2 10 Type B 0 4 4 9 4 11 Type B 0 4 4 10 4

In Table 29, K0, Sx (x=1, 2, 3, 4), and Lx (x=1, 2, 3, 4) may mean a slot granularity distance from a slot receiving the DCI to a slot in which the PDSCH is actually scheduled, a start symbol location of a scheduling resource based on a start time point of the slot for an x-th transmission occasion, and the number of symbols continuously scheduled from Sx for the x-th transmission occasion, respectively.

The proposed scheme like the example of Table 29 has the following feature.

First, the number of different transmission occasions may be indicated. Referring to Table 29, row index 1/3/4/5 indicates a transmission occasion number corresponding to 2, row index 7 indicates a transmission occasion number corresponding to 3, and row index 2/8 indicates a transmission occasion number corresponding to 4.

Second, mini-slots having different symbol lengths may be assigned to different transmission occasions. Referring to Table 29, row index 7/8 may be indicated for a transmission occasion in which a mini-slot having a symbol length of 2 and a mini-slot having a symbol length of 4 are different.

Third, whether there is the gap symbol between different transmission occasions or/and a length of the gap symbol may be indicated. Referring to Table 29, when resource assignments of row indexes 1 and 9 are compared, the resource assignments are the same in that two transmission occasions are indicated, and the start symbol of the first transmission occasion is the same and two symbols are assigned to each transmission occasion, but different in that whether there is the gap symbol between the first transmission occasion and the second transmission occasion. That is, in row index 1, there is no gap symbol and in row index 9, there is the gap symbol. It may be confirmed that there is a difference for whether there is one gap symbol between different transmission occasions even in row indexes #4 and #10. Meanwhile, when row indexes 10 and 11 are compared, it may be confirmed that the length of the gap symbol may be indicated. It may be confirmed that in the case of row index 10, there is one gap symbol between different transmission occasions, while in the case of row index 11, there are two gap symbols.

In the proposal, the ‘time domain resource assignment’ field is assumed as the DCI field for indicating one value of the time resource assignment candidates, but it is apparent that a method for applying the proposal by using another field in the DCI is also possible. For example, a new DCI field may be introduced in order to perform the proposed scheme or the proposed method may be applied by differing interpretation of a specific field among the fields in the DCI defined in the current standard. For example, the proposed method may be applied by differing the antenna port(s) field defined in TS 38.212 or/and the MCS/RV/NDI field corresponding to each of TB 1/2.

Further, as in the method and/or embodiments of Proposal 3 described above, when the repeated transmission is performed in the time domain, a DMRS pattern for transmission occasions which are repeatedly transmitted may be determined as follows. A DMRS pattern for the first transmission occasion may be indicated through the DCI, and a DMRS pattern for the other transmission occasion may adopt a pattern which is the same as the DMRS pattern for the first transmission occasion indicated through the DCI.

FIG. 17 illustrates an example of application of a DMRS pattern to repeatedly transmitted transmission occasions.

<Proposal 4>

A TCI state field (i.e., a transmission configuration indication field) in the current DCI may indicate up to two TCI states through a specific codepoint. In this case, the eMBB operation is assumed. In other words, the specific codepoint configured through the TCI field in the DCI may correspond to multiple (e.g., two) TCI states, and the eMBB operation is defined in such a manner that up to two TCI states may be indicated by the specific codepoint. In this case, when the URLLC operation is considered, improvement for some operations may be considered. The reason is that it may be preferable to indicate more TCI states in the case of the URLLC operation.

For example, it may be considered that a diversity gain is increased by increasing the repeated transmission number in the URLLC operation and the reception SNR is enhanced. Accordingly, multiple TCI states need to be considered, and a limitation for up to two TCI states defined by assuming eMBB may be alleviated. In this case, codepoints mapped to the TCI state field for the eMBB operation and codepoints mapped to the TCI state field for the URLLC operation may be differently/separately configured.

For example, the codepoints mapped to the TCI state field for the eMBB operation may indicate up to two TCI states, while the codepoints mapped to the TCI state field for the URLLC operation may be configured to indicate up to four TCI states. In the example, the number of up to four TCI states is just an example for convenience of description, and does not limit the technical scope of the present disclosure, and four or more TCI states may also be indicated.

To this end, the BS may configure/indicate whether the relevant operation is the eMBB operation or the URLLC operation, and it may be determined which codepoints configuration the UE is to follow based on the configured operation. In the proposal, as the method for configuring/indicating the eMBB operation or the URLLC operation to the UE, the method of Proposal 1 described above may be applied. For example, a specific repeated transmission method (scheme) among multiple repeated transmission methods may be configured through the higher layer signaling, and whether the URLLC operation (repeated transmission) is to be performed or the eMBB operation is to be performed actually may be indicated through the DCI. Alternatively, one of the eMBB and URLLC operations may be configured directly through a specific higher layer parameter.

Alternatively, a specific operation of the eMBB operation and the URLLC operation may be indicated according to an RNTI value to succeed in decoding the PDCCH by mapping a specific RNTI value and a specific operation. For example, when CRC masking of the DCI received by the UE is performed by using the RNTI configured as a usage of the MTRP-URLLC, the UE may recognize that the URLLC operation is configured and when the CRC masking of the DCI is performed by using the RNTI configured as a usage of the MTRP-eMBB, the UE may recognize that the eMBB operation is configured.

The example of the signaling may become one example for applying the proposed scheme, and it is apparent that other examples to which the proposed scheme is applied may also be included in the proposal, and a method to which a relevant proposed matter may be applied is not limited to the example.

The TCI state corresponding to each codepoint of the TCI field may be pre-defined, and defined differently for each of the URLLC operation and the eMBB operation. For example, the BS configures the TCI field value to the UE separately for Tables 30 and 31, and uses Table 30 in the case of the eMBB operation and Table 31 in the case of the URLLC operation. In the example, the mapping relationship between the codepoint of the DCI and the TCI state is represented by the table, but a mapping rule of another form may also be configured.

The TCI field value may be configured by using the MAC CE in a pool of up to 64 TCI states which are RRC-configured, and MAC CE for configuring the TCI field value for eMBB and MAC CE for configuring the URLLC TCI field value may be defined and signaled divisively/separately. Furthermore, the TCI states pools for the eMBB and the URLLC may also be configured separately.

TABLE 30 TCI field codepoint TCI state 000 0 001 1 010 2 011 0, 1 100 0, 2 101 1, 2 110 3 111 4

TABLE 31 TCI field codepoint TCI state 000 0, 1 001 2, 5 010 4, 5, 6, 7 011 8, 9, 10, 11 100 0, 1, 2, 3 101 0, 2, 4, 6 110 1, 3, 5, 7 111 10, 20

FIG. 18 illustrates signaling when a UE receives single DCI (i.e., when a representative TRP transmits a DCI to the UE) in a situation of M-TRP (or M-cell, all the TRPs may be hereinafter replaced by cells, or assumed as M-TRP even when a plurality of CORESETs (/CORESET groups) is configured from one TRP). FIG. 18 illustrates merely an example for convenience of explanation and does not limit the technical scope of the present disclosure.

Although the following description will be given with respect to “TRP”, “TRP” may be replaced with other expressions such as a panel, an antenna array, a cell (e.g., macro cell/small cell/pico cell), a TP (transmission point), and a base station (gNB). Also, as described above, the TRPs may be divided according to information (e.g., index, ID) on a CORESET group (or CORESET pool). For example, if one UE is configured to perform transmission and reception to and from multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for one UE. Such a configuration for CORESET groups (or CORESET pools) may be performed via higher layer signaling (e.g., RRC signaling).

Referring to FIG. 18, signaling between two TRPs and the UE is considered for the convenience of explanation, but this signaling method can be extendedly applied to signaling between multiple TRPs and multiple UEs. In the description below, a network side may be a base station including a plurality of TRPs or a cell including a plurality of TRPs. For example, ideal/non-ideal backhaul may be configured between TRP 1 and TRP 2 constituting the network side. Further, the description below is described based on multiple TRPs, but this can be extendedly applied to transmission through multiple panels. In addition, in the present disclosure, an operation for a UE to receive a signal from TRP1/TRP2 may be interpreted/described as (or may be) an operation for the UE to receive a signal from the network side (through/using TRP1/TRP2), and an operation for the UE to transmit a signal to TRP1/TRP2 may be interpreted/described as (or may be) an operation for the UE to transmit a signal to the network side (through/using TRP1/TRP2), and they may be interpreted/described in an inversed manner.

The UE may receive configuration information related to multiple TRP-based transmission and reception through/using TRP 1 (and/or TRP 2) from a network side (S1805). That is, the network side may transmit configuration information related to multiple TRP transmission and reception to the UE through/using TRP 1 (and/or TRP 2) (S1805). The configuration information may include information related to the configuration of the network side (i.e., TRP configuration), resource information related to multiple TRP-based transmission and reception (resource allocation), and so on. The configuration information may be delivered through higher-layer signaling (e.g., RRC signaling, MAC-CE, etc.). Also, if the configuration information is predefined or preset, the corresponding step may be omitted.

For example, the configuration information may include CORESET related configuration information (e.g., ControlResourceSet IE) as described in the above-described methods (e.g., proposal 1/proposal 2/proposal 3/proposal 4, etc.). The CORESET related configuration information may include a CORESET related ID (e.g., controlResourceSetID), an index of a CORESET pool for CORESET (e.g., CORESETPoolIndex), time/frequency resource configuration of CORESET, TCI information related to CORESET, and the like. The index of the CORESET pool (e.g., CORESETPoolIndex) may mean a specific index (e.g., CORESET group Index, HARQ Codebook index) mapped/configured to each CORESET.

For example, the configuration information may also include configurations related to PDCCH/PDSCH/PUCCH/PUSCH, etc., as described in the methods (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.).

For example, the configuration information may include information representing which operation is to be performed among multiple URLLC operations according to the method and/or embodiment (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.). As an example, the configuration information may include information for configuring one of the URLLC schemes (e.g., scheme 2a/2b/3/4).

For example, the configuration information may include configuration information for a TCI state configuration related to the operation of the method and/or embodiment (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.)/configuration information related to specific repeated transmission related to the URLLC/information on a value(s) for the repeated transmission number of the transmission occasion and/or a candidate value(s)/the number of shifting symbols between different transmission occasions/information related to RV values, etc.

For example, the operation of the UE (reference numeral 100/200 in FIGS. 21 to 25) which receives the multiple TRP based transmission and reception related configuration information from the network side (reference numeral 100/200 in FIGS. 21 to 25) in step S1805 described above may be implemented by devices in FIGS. 21 to 25 to be described below. For example, referring to FIG. 22, one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 so as to receive the multiple TRP based transmission and reception related configuration information, and one or more transceivers 106 may receive configuration information and one or more transceivers 106 may receive the multiple TRP based transmission and reception related configuration information from the network side.

Likewise, the operation of the network side (reference numeral 100/200 in FIGS. 21 to 25) which transmits the multiple TRP based transmission and reception related configuration information to the UE (reference numeral 100/200 in FIGS. 21 to 25) in step S1805 described above may be implemented by the devices in FIGS. 21 to 25 to be described below. For example, referring to FIG. 22, one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 so as to transmit the multiple TRP based transmission and reception related configuration information, and one or more transceivers 106 may receive configuration information and one or more transceivers 106 may transmit the multiple TRP based transmission and reception related configuration information from the network side.

The UE may receive, from the network side, DCI and Data 1 scheduled by corresponding DCI through/using TRP 1 (S1810-1). Further, the UE may receive Data 2 from the network side through/using TRP 2 (S1810-2). That is, the network side may transmit, to the UE, DCI 1 and Data 1 scheduled by corresponding DCI through/using TRP 1 (S1810-1). Further, the network side may transmit Data 2 to the UE through/using TRP 2 (S1810-2). For example, DCI and Data (e.g., Data 1, Data 2) may be transferred through a control channel (e.g., PDCCH, etc.) and a data channel (e.g., PDSCH, etc.), respectively. Further, steps S1810-1 and S1810-2 may be simultaneously performed or any one may be performed earlier than the other one.

For example, the DCI may include a TCI field, an antenna port(s) field, a time domain resource assignment field, an MCS field, and an RV field.

For example, the DCI may include information representing whether the URLLC operation configured to the UE through the higher layer signaling is performed which operation is to be performed as described in the method and/or embodiment (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.). In this case, a specific bit of a DMRS port indication field in the DCI may be used. For example, the DCI may include information representing a total repeated transmission number. In this case, the relevant repeated transmission number may be determined according to the number of TCI states indicated through the DCI. For example, the DCI may also include the number of shifting symbols between different transmission occasions/information related to RV values (e.g., the actual RV difference value/the difference value in the order/the actual RV value/the RV combination related indication information). For example, the DCI may include information representing a time domain resource of repeatedly transmitted data. As an example, the DCI may include information indicating the mini-slot granularity repeated transmission/information representing whether the mini-slot granularity repeated transmission is performed. For example, the interpretation of the TCI state field in the DCI may be determined according to whether the eMBB operation being configured or the URLLC operation being configured.

For example, the DCI may be configured to be used for scheduling for both Data 1 and Data 2, and may indicate that Data 1 and Data 2 are the same data having the same systematic bits, as described in the method and/or embodiment (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.). In other words, Data 1 and Data 2 may correspond to the same TB.

For example, the operation of the UE (reference numeral 100/200 in FIGS. 21 to 25) which receives the DCI and/or Data 1 and/or Data 2 from the network side (reference numeral 100/200 in FIGS. 21 to 25) in step S1810-1/S1810-2 described above may be implemented by the devices in FIGS. 21 to 25 to be described below. For example, referring to FIG. 22, one or more processor 102 may control one or more transceivers 106 and/or one or more memories 104 to receive the DCI and/or Data 1 and/or Data 2, and one or more transceivers 106 may receive, from the network side, the DCI and/or Data 1 and/or Data 2.

Likewise, the operation of the network side (reference numeral 100/200 in FIGS. 21 to 25) which transmits the DCI and/or Data 1 and/or Data 2 to the UE (reference numeral 100/200 in FIGS. 21 to 25) in step S1810-1/S1810-2 described above may be implemented by the devices in FIGS. 21 to 25 to be described below. For example, referring to FIG. 22, one or more processor 102 may control one or more transceivers 106 and/or one or more memories 104 to transmit the DCI and/or Data 1 and/or Data 2, and one or more transceivers 106 may transmit, to the UE, the DCI and/or Data 1 and/or Data 2.

The UE may decode Data 1 and Data 2 received from TRP 1 and TRP 2 (S1815). For example, the UE may perform channel estimation and/or decoding for data based on the method (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.).

For example, the UE may know that the BS transmits the same data according to a specific URLLC operation, and decode Data 1 and Data 2 by assuming that Data 1 and Data 2 are the same data and systematic bits are the same data, as described in the proposed method and/or embodiment (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.). For example, the UE may decode Data 1 and Data 2 by considering a repeated transmission number indicated by the BS through the higher layer signaling/DCI. As an example, the UE may decode Data 1 and Data 2 by assuming that the BS repeatedly transmits the same data as large as the number of TCI states indicated through the DCI. For example, the UE may decode Data 1 and Data 2 (repeatedly transmitted in one slot) based on the number of shifting symbols between different transmission occasions/the information related to RV values (e.g., the actual RV difference value/the difference value in the order/the actual RV value/the RV combination related indication information). For example, the UE may decode Data 1 and Data 2 by assuming that the BS repeatedly transmits the same data in a time domain indicated through the DCI. For example, the UE may decode Data 1 and Data 2 by using the TCI state value which the BS indicates through the DCI.

For example, the operation of the UE (reference numeral 100/200 of FIGS. 21 to 25) which decodes Data 1 and Data 2 in step S1815 described above may be implemented by the devices of FIGS. 21 to 25 to be described below. For example, referring to FIG. 22, one or more processor 102 may control one or more memories 104 to perform the operation of decoding Data 1 and Data 2.

The UE may transmit HARQ-ACK information (e.g., ACK information, NACK information, etc.) for the DCI and/or Data 1 and/or Data 2 above to the network side through/using TRP 1 and/or TRP 2 through one or more PUCCH(s) based on the proposed method (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.) (S1820-1 and S1820-2). That is, the network side may receive, from the UE, HARQ-ACK information (e.g., ACK information, NACK information, etc.) for the DCI and/or Data 1 and/or Data 2 above through/using TRP 1 and/or TRP 2 through one or more PUCCH(s) based on the proposed method (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.) (S1820-1 and S1820-2).

For example, the HARQ-ACK information for Data 1 and/or Data 2 may be combined into one or separated. Further, the UE may be configured to transmit only HARQ-ACK information to representative TRP (e.g., TRP 1), and transmission of the HARQ-ACK information to the other TRP (e.g., TRP 2) may also be omitted. For example, the HARQ-ACK information may be transmitted through the PUCCH and/or the PUSCH.

For example, the operation of the UE (reference numeral 100/200 in FIGS. 21 to 21) which transmits the HARQ-ACK information for Data 1 and/or Data 2 to the network side (reference numeral 100/200 in FIGS. 21 to 25) through one or more PUCCHs in step S1820-1/S1820-2 described above may be implemented by the devices in FIGS. 21 to 25 to be described below. For example, referring to FIG. 22, one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to transmit the HARQ-ACK information for Data 1 and/or Data 2 through one or more PUCCHs, and one or more transceivers 106 may transmit, to the network side, the HARQ-ACK information for Data 1 and/or Data 2.

Likewise, the operation of the network side (reference numeral 100/200 in FIGS. 21 to 25) which receives the HARQ-ACK information for Data 1 and/or Data 2 from the UE (reference numeral 100/200 in FIGS. 21 to 25) through one or more PUCCHs in step S1820-1/S1820-2 described above may be implemented by the devices in FIGS. 21 to 25 to be described below. For example, referring to FIG. 22, one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to receive the HARQ-ACK information for Data 1 and/or Data 2, and one or more transceivers 106 may receive, from the UE, the HARQ-ACK information for Data 1 and/or Data 2.

In FIG. 18 described above, the methods are described based on a single DCI based M-TRP operation is primarily described, but in some cases, the methods may be applied even to a multi-DCI based M-TRP operation.

FIG. 19 illustrates an example of an operation flowchart of downlink data reception of a UE to which methods (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.) proposed in the present disclosure may be applied. The UE may be supported by a plurality of TRPs, and ideal/non-ideal backhaul may be configured among the plurality of TRPs. FIG. 19 is just for convenience of the description and does not limit the scope of the present disclosure. Further, some step(s) illustrated in FIG. 19 may be omitted according to a situation and/or a configuration.

In the following description, the network side is described based on “TRP”, but as described above, “TRP” may be replaced with expressions including a panel, an antenna array, a cell (e.g., macro cell/small cell/pico cell), a transmission point (TP), a base station (gNB, etc.), etc., and applied. Further, as described above, the TRP may be distinguished according to information (e.g., an index or ID) on a CORESET group (or CORESET pool). As an example, when one UE is configured to perform transmission/reception with multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for one UE. The configuration for the CORESET group (or CORESET pool) may be performed through the higher layer signaling (e.g., RRC signaling).

The UE may receive configuration information (S1910). The configuration information may be received through a higher layer signaling (e.g., RRC or MAC-CE). The configuration information may include information related to a method and/or embodiments described in the methods (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.).

For example, the configuration information may include CORESET related configuration information (e.g., ControlResourceSet IE). The CORESET related configuration information may include ID (e.g., controlResourceSetID) related to the CORESET, an index (e.g., CORESETPoolIndex) of a CORESET pool for the CORESET, a time/frequency resource configuration of the CORESET, TCI information related to the CORESET, etc.

For example, the configuration information may include a downlink channel related configuration (e.g., PDCCH-Config, PDSCH-Config). The downlink channel related configuration may include DMRS maxLength, a configuration type, a mapping type, etc.

For example, the configuration information may include information on a transmission scheme of downlink data. Based on the information on the downlink data transmission scheme, an eMBB operation or a URLLC operation may be configured or one of multiple schemes (e.g., an SDM scheme, a TDM scheme, or an FDM scheme) related to the URLLC operation may be indicted/configured. As an example, the configuration information may include a higher layer parameter (e.g., RepSchemeEnabler) for indicating one of the schemes for the URLLC operation, and whether the relevant scheme is an FDM based scheme (e.g., scheme 2a/2b) or a TDM based scheme (scheme 3/4) may be configured by using the higher layer parameter. As a specific example, a repetition scheme based on time division multiplexing (TDM) may be configured based on the configuration information.

For example, the configuration information may include information related to the number of transmission occasions. As an example, the configuration information may include a parameter (e.g., repetitionnumber) for configuring a repeated transmission number of the transmission occasions, and a specific repetition number (e.g., 2, 3, 4, 5, 6, 7, 8, or 16) may be indicated by the parameter. As another example, candidate values of the number of plurality of transmission occasions may be indicated based on the configuration information.

For example, the configuration information may include information on the number of shifting symbols between transmission occasions. The shifting symbol may be replaced with an expression such as a gap symbol or a symbol offset. As an example, the shifting symbol may mean a gap between a last symbol of a first transmission occasion and a first symbol of a second transmission occasion.

For example, an operation of the UE (reference numeral 100/200 in FIGS. 21 to 25) which receives the configuration information in step S1930 described above may be implemented by the devices in FIGS. 21 to 25 to be described below. For example, referring to FIG. 22, one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 so as to transmit the configuration information and one or more transceivers 106 may receive the configuration information.

The UE may receive downlink control information (DCI) (S1920). The DCI may be transmitted through a downlink control channel (e.g., PDCCH).

As described in the method (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.), the DCI may include at least one of a DMRS port related field (e.g., antenna port(s) field), a transport block related field (e.g., MCS/New data indicator/RV field), a transmission configuration indication (TCI) field, a time domain resource assignment field, or a redundancy version (RV) field.

For example, a plurality of TCI states may be indicated based on the TCI field included in the DCI. When the plurality of TCI states is indicated, the UE may know that the relevant operation is an M-TRP operation. As an example, two or more TCI states may be indicated in relation to a URLLC M-TRP operation.

For example, resource assignment in a time domain for a first transmission occasion may be determined based on the time domain resource assignment field included in the DCI. Further, the resource assignment in the time domain for a second transmission occasion may be determined based on the resource assignment in the time domain for the first transmission occasion. Through this, even though resource assignment information in the time domain for the second transmission occasion is not included in the DCI, the resource assignment in the time domain for the second transmission occasion may be determined. Through this, signaling overhead may be reduced and compatibility with a conventional DCI format may also be secured.

As a specific example, a size of a second resource in the time domain for the second transmission occasion may be determined based on a size of a first resource in the time domain for the first transmission occasion. Further, the size of the first resource and the size of the second resource may be equal to each other. That is, the size of the second resource may be determined as a size which is the same as the size of the first resource. As an example, the number of symbols for the first transmission occasion may be equal to the number of symbols of the second transmission occasion.

For example, the first resource and the second resource may be constituted as a unit of 2, 4, or 7 OFDM symbols. The first resource and the second resource may be positioned in concatenation with each other in the time domain. Alternatively, a first symbol of the second resource may be positioned from a last symbol of the first resource after a specific number of symbols. In this case, in the UE operation of FIG. 19, the method may further include receiving information on the specific number of symbols. As an example, the information on the specific number of symbols may also be received while being included in the configuration information.

For example, an operation of the UE (reference numeral 100/200 in FIGS. 21 to 25) which receives the DCI in step S1940 described above may be implemented by the devices in FIGS. 21 to 25 to be described below. For example, referring to FIG. 22, one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 so as to receive the DCI and one or more transceivers 106 may receive the DCI.

The UE may receive a plurality of transmission occasions (S1950). The plurality of transmission occasions may be received based on the DCI. For example, an operation of receiving the transmission occasion may be interpreted/appreciated as an operation of receiving downlink data or an operation of receiving a downlink channel.

For example, the plurality of transmission occasions may be the same PDSCH transmission occasion being repeatedly transmitted/received, as described in the method (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.). In other words, the plurality of transmission occasions may correspond to the same transport block.

For example, the number of plurality of transmission occasions may be determined based on the number of TCI states indicated through the TCI field of the DCI. As described above, since the plurality of transmission occasions may be constituted by repeatedly transmitting the transmission occasion corresponding to the same transport block, the number of plurality of transmission occasions may mean the number of times at which the transmission occasion is repeatedly transmitted. As an example, when the plurality of ICI states is indicated through the TCI field of the DCI (e.g., 2 TCI states), the number of transmitted/received transmission occasions may also be equal to the number of plurality of TCI states (e.g., 2 transmission occasions).

As a specific example, when a first TCI state and a second TCI state are indicated through the TCI field of the DCI, the UE may receive two, i.e., a first transmission occasion and a second transmission occasion. In this case, the first TCI state may correspond to the first transmission occasion and the second TCI state may correspond to the second transmission occasion. Further, the RV value of the first transmission occasion and the RV value of the second transmission occasion may be configured differently based on the RV field of the DCI.

As another example, the number of plurality of transmission occasions may also be determined based on the configuration information and the DCI. As an example, candidate values of the number of plurality of transmission occasions may be indicated based on the configuration information, and one value of the candidate values may be indicated/configured based on the DCI.

For example, the plurality of transmission occasions (e.g., the first transmission occasion and the second transmission occasion) may be received in a time domain resource based on time division multiplexing (TDM). That is, the plurality of transmission occasions may be repeatedly received/transmitted in a time domain resource which is not overlapped based on the TDM.

For example, each transmission occasion may be constituted by 2, 4, or 7 OFDM symbols. This may correspond to the min-slot structure of PDSCH mapping type B described in the proposed method (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.) described above. The plurality of transmission occasions (e.g., the first transmission occasion and the second transmission occasion) may be TDMed and received in one slot. Alternatively, each transmission occasion may be TDMed and received as a unit of slot.

For example, the plurality of transmission occasions may be received in the resource of the time domain determined based on the DCI. As an example, the first transmission occasion may be receive din a first time domain resource and the second transmission occasion may be received in a second time domain resource. The first time domain resource and the second time domain resource may be positioned in concatenation with each other. Alternatively, the second time domain resource may also be positioned apart from the first time domain resource by a specific number of symbols. The specific number of symbols may be replaced with the gap symbol/the shifting symbol/the symbol offset, and expressed. The specific number of symbols may be received through the higher layer signaling.

For example, the number of transmission layers may also be limited to a specific layer number (e.g., 2 layers) or less for each transmission occasion.

For example, an operation of the UE (reference numeral 100/200 in FIGS. 21 to 25) which receives the plurality of transmission occasions in step S1930 described above may be implemented by the devices in FIGS. 21 to 25 to be described below. For example, referring to FIG. 22, one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 so as to receive the plurality of transmission occasions, and one or more transceivers 106 may receive the plurality of transmission occasions.

FIG. 20 illustrates an example of an operation flowchart of a base station (BS) performing data transmission and reception to which the methods (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.) may be applied. FIG. 20 is just for convenience of the description and does not limit the scope of the present disclosure. Further, some step(s) illustrated in FIG. 20 may be omitted according to a situation and/or a configuration.

The BS may be a mean collecting naming an object performing transmission and reception of data with the UE. For example, the base station may be a concept including one or more transmission points (TPs), one or more transmission and reception points (TRPs), and the like. Further, the TP and/or the TRP may include a panel, transmission and reception units, and the like of the BS. Further, as described above, the TRP may be distinguished according to information (e.g., an index or ID) on a CORESET group (or CORESET pool). As an example, when one UE is configured to perform transmission/reception with multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for one UE. The configuration for the CORESET group (or CORESET pool) may be performed through the higher layer signaling (e.g., RRC signaling).

The BS may transmit, to the UE, configuration information (S2010). The configuration information may be transmitted through a higher layer signaling (e.g., RRC or MAC-CE). The configuration information may include information related to a method and/or embodiments described in the methods (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.).

For example, the configuration information may include CORESET related configuration information (e.g., ControlResourceSet IE). The CORESET related configuration information may include ID (e.g., controlResourceSetID) related to the CORESET, an index (e.g., CORESETPoolIndex) of a CORESET pool for the CORESET, a time/frequency resource configuration of the CORESET, TCI information related to the CORESET, etc.

For example, the configuration information may include a downlink channel related configuration (e.g., PDCCH-Config, PDSCH-Config). The downlink channel related configuration may include DMRS maxLength, a configuration type, a mapping type, etc.

For example, the configuration information may include information on a transmission scheme of downlink data. Based on the information on the downlink data transmission scheme, an eMBB operation or a URLLC operation may be configured or one of multiple schemes (e.g., an SDM scheme, a TDM scheme, or an FDM scheme) related to the URLLC operation may be indicted/configured. As an example, the configuration information may include a higher layer parameter (e.g., RepSchemeEnabler) for indicating one of the schemes for the URLLC operation, and whether the relevant scheme is an FDM based scheme (e.g., scheme 2a/2b) or a TDM based scheme (scheme 3/4) may be configured by using the higher layer parameter. As a specific example, a repetition scheme based on time division multiplexing (TDM) may be configured based on the configuration information.

For example, the configuration information may include information related to the number of transmission occasions. As an example, the configuration information may include a parameter (e.g., repetitionnumber) for configuring a repeated transmission number of the transmission occasions, and a specific repetition number (e.g., 2, 3, 4, 5, 6, 7, 8, or 16) may be indicated by the parameter. As another example, candidate values of the number of plurality of transmission occasions may be indicated based on the configuration information.

For example, the configuration information may include information on the number of shifting symbols between transmission occasions. The shifting symbol may be replaced with an expression such as a gap symbol or a symbol offset. As an example, the shifting symbol may mean a gap between a last symbol of a first transmission occasion and a first symbol of a second transmission occasion.

For example, an operation of the BS (reference numeral 100 and/or 200 in FIGS. 21 to 25) which transmits the configuration information in step S2010 described above may be implemented by the devices in FIGS. 21 to 25 to be described below. For example, referring to FIG. 22, one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 so as to transmit the configuration information and one or more transceivers 106 may transmit the configuration information.

The BS may transmit, to the UE, downlink control information (DCI) (S2040). The DCI may be transmitted through a downlink control channel (e.g., PDCCH).

As described in the method (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.), the DCI may include at least one of a DMRS port related field (e.g., antenna port(s) field), a transport block related field (e.g., MCS/New data indicator/RV field), a transmission configuration indication (TCI) field, a time domain resource assignment field, or a redundancy version (RV) field.

For example, a plurality of TCI states may be indicated based on the TCI field included in the DCI. When the plurality of TCI states is indicated, the UE may know that the relevant operation is an M-TRP operation. As an example, two or more TCI states may be indicated in relation to a URLLC M-TRP operation.

For example, resource assignment in a time domain for a first transmission occasion may be determined based on the time domain resource assignment field included in the DCI. Further, the resource assignment in the time domain for a second transmission occasion may be determined based on the resource assignment in the time domain for the first transmission occasion. Through this, even though resource assignment information in the time domain for the second transmission occasion is not included in the DCI, the resource assignment in the time domain for the second transmission occasion may be determined. Through this, signaling overhead may be reduced and compatibility with a conventional DCI format may also be secured.

As a specific example, a size of a second resource in the time domain for the second transmission occasion may be determined based on a size of a first resource in the time domain for the first transmission occasion. Further, the size of the first resource and the size of the second resource may be equal to each other. That is, the size of the second resource may be determined as a size which is the same as the size of the first resource.

For example, the first resource and the second resource may be constituted as a unit of 2, 4, or 7 OFDM symbols. The first resource and the second resource may be positioned in concatenation with each other in the time domain. Alternatively, a first symbol of the second resource may be positioned from a last symbol of the first resource after a specific number of symbols. In this case, in the BS operation of FIG. 20, the method may further include transmitting information on the specific number of symbols. As an example, the information on the specific number of symbols may also be transmitted while being included in the configuration information.

For example, an operation of the BS (reference numeral 100/200 in FIGS. 21 to 25) which transmits the DCI in step S2020 described above may be implemented by the devices in FIGS. 21 to 25 to be described below. For example, referring to FIG. 22, one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 so as to transmit the DCI and one or more transceivers 106 may transmit the DCI.

The BS may transmit a plurality of transmission occasions (S2050). The plurality of transmission occasions may be transmitted based on the DCI.

For example, the plurality of transmission occasions may be the same PDSCH transmission occasion being repeatedly transmitted/received, as described in the method (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.). In other words, the plurality of transmission occasions may correspond to the same transport block.

For example, the number of plurality of transmission occasions may be determined based on the number of TCI states indicated through the TCI field of the DCI. As described above, since the plurality of transmission occasions may be constituted by repeatedly transmitting the transmission occasion corresponding to the same transport block, the number of plurality of transmission occasions may mean the number of times at which the transmission occasion is repeatedly transmitted. As an example, when the plurality of TCI states is indicated through the TCI field of the DCI (e.g., 2 TCI states), the number of transmitted/received transmission occasions may also be equal to the number of plurality of TCI states (e.g., 2 transmission occasions).

As a specific example, when a first TCI state and a second TCI state are indicated through the TCI field of the DCI, the UE may receive two, i.e., a first transmission occasion and a second transmission occasion. In this case, the first TCI state may correspond to the first transmission occasion and the second TCI state may correspond to the second transmission occasion. Further, the RV value of the first transmission occasion and the RV value of the second transmission occasion may be configured differently based on the RV field of the DCI.

As another example, the number of plurality of transmission occasions may also be determined based on the configuration information and the DCI. As an example, candidate values of the number of plurality of transmission occasions may be indicated based on the configuration information, and one value of the candidate values may be indicated/configured based on the DCI.

For example, the plurality of transmission occasions (e.g., the first transmission occasion and the second transmission occasion) may be received in a time domain resource based on time division multiplexing (TDM). That is, the plurality of transmission occasions may be repeatedly received/transmitted in a time domain resource which is not overlapped based on the TDM.

For example, each transmission occasion may be constituted by 2, 4, or 7 OFDM symbols. This may correspond to the min-slot structure of PDSCH mapping type B described in the proposed method (e.g., Proposal 1/Proposal 2/Proposal 3/Proposal 4, etc.) described above. The plurality of transmission occasions (e.g., the first transmission occasion and the second transmission occasion) may be TDMed and received in one slot. Alternatively, each transmission occasion may be TDMed and received as a unit of slot.

For example, the plurality of transmission occasions may be received in the resource of the time domain determined based on the DCI. As an example, the first transmission occasion may be receive din a first time domain resource and the second transmission occasion may be received in a second time domain resource. The first time domain resource and the second time domain resource may be positioned in concatenation with each other. Alternatively, the second time domain resource may also be positioned apart from the first time domain resource by a specific number of symbols. The specific number of symbols may be replaced with the gap symbol/the shifting symbol/the symbol offset, and expressed. The specific number of symbols may be received through the higher layer signaling.

For example, an operation of the BS (reference numeral 100 and/or 200 in FIGS. 21 to 25) which transmits a plurality of transmission occasions in step S2050 described above may be implemented by the devices in FIGS. 21 to 25 to be described below. For example, referring to FIG. 22, one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 so as to transmit the plurality of transmission occasions, and one or more transceivers 106 may transmit the plurality of transmission occasions.

As mentioned above, the network side/UE signaling and operation (e.g., Proposal 1/2/3/4, FIG. 18/19/20, etc.) may be implemented by devices (e.g., FIGS. 21 to 25) to be described below. For example, the network side (e.g., TRP 1/TRP 2) may correspond to a first wireless device and the UE may correspond to a second wireless device and in some cases, an opposite case thereto may also be considered. For example, the first device (e.g., TRP 1)/the second device (e.g., TRP 2) may correspond to the first wireless device and the UE may correspond to the second wireless device and in some cases, an opposite case thereto may also be considered.

For example, the network side/UE signaling/operation (e.g., Proposal 1/2/3/4/FIG. 18/19/20, etc.) may be processed by one or more processors (e.g., 102 and 202) in FIGS. 21 to 25 and the network side/UE signaling and operation (e.g., Proposal 1/2/3/4/FIG. 18/19/20, etc.) may be stored in one or more (e.g., 104 and 204) of FIG. 21) in the form of a command/program (e.g., instruction and executable code) for driving at least one processor (e.g., 102 and 202) in FIGS. 21 to 25.

According to an embodiment of the present disclosure, in a device including: one or more memories and one or more processors functionally connected to the one or more memories, the one or more processors may be configured to control the device to transmit a preamble for random access, receive a response message for the random access corresponding to the preamble, a radio remote control (RRC) connection being established based on the preamble and the response message, receive configuration information, receive downlink control information (DCI) including a time domain resource assignment field, and receive a plurality of transmission occasions based on the DCI, a repetition scheme based on time division multiplexing (TDM) may be configured based on the configuration information, a first transmission occasion and a second transmission occasion included in the plurality of transmission occasions may correspond to the same transport block, the first transmission occasion and the second transmission occasion may be received in different resources of a time domain based on TDM, resource assignment in the time domain for the first transmission occasion may be determined based on the time domain resource assignment field of the DCI, and the resource assignment in the time domain for the second transmission occasion may be determined based on the resource assignment in the time domain for the first transmission occasion.

According to an embodiment of the present disclosure, in one or more non-transitory computer-readable media storing one or more instructions, the one or more instructions executable by one or more processors may include instructions for instructing a user equipment (UE) to transmit a preamble for random access, receive a response message for the random access corresponding to the preamble, a radio remote control (RRC) connection being established based on the preamble and the response message, receive configuration information, receive downlink control information (DCI) including a time domain resource assignment field, and receive a plurality of transmission occasions based on the DCI, a repetition scheme based on time division multiplexing (TDM) may be configured based on the configuration information, a first transmission occasion and a second transmission occasion included in the plurality of transmission occasions may correspond to the same transport block, the first transmission occasion and the second transmission occasion may be received in different resources of a time domain based on TDM, resource assignment in the time domain for the first transmission occasion may be determined based on the time domain resource assignment field of the DCI, and the resource assignment in the time domain for the second transmission occasion may be determined based on the resource assignment in the time domain for the first transmission occasion.

Communication System Applied to the Present Disclosure

The various descriptions, functions, procedures, proposals, methods, and/or operational flowcharts of the present disclosure described in this document may be applied to, without being limited to, a variety of fields requiring wireless communication/connection (e.g., 5G) between devices.

Hereinafter, a description will be given in more detail with reference to the drawings. In the following drawings/description, the same reference symbols may denote the same or corresponding hardware blocks, software blocks, or functional blocks unless described otherwise.

FIG. 21 illustrates a communication system applied to the present disclosure.

Referring to FIG. 21, a communication system applied to the present disclosure includes wireless devices, Base Stations (BSs), and a network. Herein, the wireless devices represent devices performing communication using Radio Access Technology (RAT) (e.g., 5G New RAT (NR)) or Long-Term Evolution (LTE)) and may be referred to as communication/radio/5G devices. The wireless devices may include, without being limited to, a robot 1010 a, vehicles 1010 b-1 and 1010 b-2, an eXtended Reality (XR) device 1010 c, a hand-held device 1010 d, a home appliance 1010 e, an Internet of Things (IoT) device 1010 f, and an Artificial Intelligence (AI) device/server 400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. Herein, the vehicles may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). The XR device may include an Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) device and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter. For example, the BSs and the network may be implemented as wireless devices and a specific wireless device 200 a may operate as a BS/network node with respect to other wireless devices.

The wireless devices 1010 a to 1010 f may be connected to the network 300 via the BSs 1020. An AI technology may be applied to the wireless devices 1010 a to 1010 f and the wireless devices 1010 a to 1010 f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 1010 a to 1010 f may communicate with each other through the BSs 1020/network 300, the wireless devices 1010 a to 1010 f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs/network. For example, the vehicles 1010 b-1 and 1010 b-2 may perform direct communication (e.g. Vehicle-to-Vehicle (V2V)/Vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 1010 a to 1010 f.

Wireless communication/connections 150 a, 150 b, or 150 c may be established between the wireless devices 1010 a to 1010 f/BS 1020, or BS 1020/BS 1020. Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication 150 a, sidelink communication 150 b (or, D2D communication), or inter BS communication (e.g. Relay, Integrated Access Backhaul (IAB)). The wireless devices and the BSs/the wireless devices may transmit/receive radio signals to/from each other through the wireless communication/connections 150 a and 150 b. For example, the wireless communication/connections 150 a and 150 b may transmit/receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure.

Devices Applicable to the Present Disclosure

FIG. 22 illustrates wireless devices applicable to the present disclosure.

Referring to FIG. 22, a first wireless device 100 and a second wireless device 200 may transmit radio signals through a variety of RATs (e.g., LTE and NR). Herein, {the first wireless device 100 and the second wireless device 200} may correspond to {the wireless device 1010 x and the BS 1020} and/or {the wireless device 1010 x and the wireless device 1010 x} of FIG. 21.

The first wireless device 100 may include one or more processors 102 and one or more memories 104 and additionally further include one or more transceivers 106 and/or one or more antennas 108. The processor(s) 102 may control the memory(s) 104 and/or the transceiver(s) 106 and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s) 102 may process information within the memory(s) 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s) 106. The processor(s) 102 may receive radio signals including second information/signals through the transceiver 106 and then store information obtained by processing the second information/signals in the memory(s) 104. The memory(s) 104 may be connected to the processor(s) 102 and may store a variety of information related to operations of the processor(s) 102. For example, the memory(s) 104 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 102 or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) 102 and the memory(s) 104 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 106 may be connected to the processor(s) 102 and transmit and/or receive radio signals through one or more antennas 108. Each of the transceiver(s) 106 may include a transmitter and/or a receiver. The transceiver(s) 106 may be interchangeably used with Radio Frequency (RF) unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip.

The second wireless device 200 may include at least one processor 202 and at least one memory 204 and additionally further include at least one transceiver 206 and/or one or more antennas 208. The processor(s) 202 may control the memory(s) 204 and/or the transceiver(s) 206 and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s) 202 may process information within the memory(s) 204 to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver(s) 206. The processor(s) 202 may receive radio signals including fourth information/signals through the transceiver(s) 206 and then store information obtained by processing the fourth information/signals in the memory(s) 204. The memory(s) 204 may be connected to the processor(s) 202 and may store a variety of information related to operations of the processor(s) 202. For example, the memory(s) 204 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 202 or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) 202 and the memory(s) 204 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 206 may be connected to the processor(s) 202 and transmit and/or receive radio signals through one or more antennas 208. Each of the transceiver(s) 206 may include a transmitter and/or a receiver. The transceiver(s) 206 may be interchangeably used with RF unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip.

Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Unit (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document.

The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors 102 and 202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of code, commands, and/or a set of commands.

The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories 104 and 204 may be configured by Read-Only Memories (ROMs), Random Access Memories (RAMs), Electrically Erasable Programmable Read-Only Memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage medium, and/or combinations thereof. The one or more memories 104 and 204 may be located at the interior and/or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.

The one or more transceivers 106 and 206 may transmit user data, control information, and/or radio signals/channels, mentioned in the methods and/or operational flowcharts of this document, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices. The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 and the one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, through the one or more antennas 108 and 208. In this document, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). The one or more transceivers 106 and 206 may convert received radio signals/channels etc. From RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc. Using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals/channels, etc. Processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and/or filters.

Signal Processing Circuit Example to which Disclosure is Applied

FIG. 23 illustrates a signal processing circuit for a transmit signal.

Referring to FIG. 23, a signal processing circuit 1000 may include a scrambler 1010, a modulator 1020, a layer mapper 1030, a precoder 1040, a resource mapper 1050, and a signal generator 1060. Although not limited thereto, an operation/function of FIG. 23 may be performed by the processors 102 and 202 and/or the transceivers 106 and 206 of FIG. 22. Hardware elements of FIG. 23 may be implemented in the processors 102 and 202 and/or the transceivers 106 and 206 of FIG. 22. For example, blocks 1010 to 1060 may be implemented in the processors 102 and 202 of FIG. 22. Further, blocks 1010 to 1050 may be implemented in the processors 102 and 202 of FIG. 22 and the block 1060 of FIG. 22 and the block 2060 may be implemented in the transceivers 106 and 206 of FIG. 22.

A codeword may be transformed into a radio signal via the signal processing circuit 1000 of FIG. 23. Here, the codeword is an encoded bit sequence of an information block. The information block may include transport blocks (e.g., a UL-SCH transport block and a DL-SCH transport block). The radio signal may be transmitted through various physical channels (e.g., PUSCH and PDSCH).

Specifically, the codeword may be transformed into a bit sequence scrambled by the scrambler 1010. A scramble sequence used for scrambling may be generated based on an initialization value and the initialization value may include ID information of a wireless device. The scrambled bit sequence may be modulated into a modulated symbol sequence by the modulator 1020. A modulation scheme may include pi/2-BPSK (pi/2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), m-QAM (m-Quadrature Amplitude Modulation), etc. A complex modulated symbol sequence may be mapped to one or more transport layers by the layer mapper 1030. Modulated symbols of each transport layer may be mapped to a corresponding antenna port(s) by the precoder 1040 (precoding). Output z of the precoder 1040 may be obtained by multiplying output y of the layer mapper 1030 by precoding matrix W of N*M. Here, N represents the number of antenna ports and M represents the number of transport layers. Here, the precoder 1040 may perform precoding after performing transform precoding (e.g., DFT transform) for complex modulated symbols. Further, the precoder 1040 may perform the precoding without performing the transform precoding.

The resource mapper 1050 may map the modulated symbols of each antenna port to a time-frequency resource. The time-frequency resource may include a plurality of symbols (e.g., CP-OFDMA symbol and DFT-s-OFDMA symbol) in a time domain and include a plurality of subcarriers in a frequency domain. The signal generator 1060 may generate the radio signal from the mapped modulated symbols and the generated radio signal may be transmitted to another device through each antenna. To this end, the signal generator 1060 may include an Inverse Fast Fourier Transform (IFFT) module, a Cyclic Prefix (CP) inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, and the like.

A signal processing process for a receive signal in the wireless device may be configured in the reverse of the signal processing process (1010 to 1060) of FIG. 23. For example, the wireless device (e.g., 100 or 200 of FIG. 22) may receive the radio signal from the outside through the antenna port/transceiver. The received radio signal may be transformed into a baseband signal through a signal reconstructer. To this end, the signal reconstructer may include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a Fast Fourier Transform (FFT) module. Thereafter, the baseband signal may be reconstructed into the codeword through a resource de-mapper process, a postcoding process, a demodulation process, and a de-scrambling process. The codeword may be reconstructed into an original information block via decoding. Accordingly, a signal processing circuit (not illustrated) for the receive signal may include a signal reconstructer, a resource demapper, a postcoder, a demodulator, a descrambler, and a decoder.

Example of a Wireless Device Applied to the Present Disclosure

FIG. 24 illustrates another example of a wireless device applied to the present disclosure. The wireless device may be implemented in various forms according to a use-case/service (see FIG. 21).

Referring to FIG. 24, wireless devices 1010 and 1020 may correspond to the wireless devices 100 and 200 of FIG. 22 and may be configured by various elements, components, units/portions, and/or modules. For example, each of the wireless devices 1010 and 2010 may include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140. The communication unit may include a communication circuit 112 and transceiver(s) 114. For example, the communication circuit 112 may include the one or more processors 102 and 202 and/or the one or more memories 104 and 104 of FIG. 22. For example, the transceiver(s) 114 may include the one or more transceivers 106 and 106 and/or the one or more antennas 108 and 108 of FIG. 22. The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140 and controls overall operation of the wireless devices. For example, the control unit 120 may control an electric/mechanical operation of the wireless device based on programs/code/commands/information stored in the memory unit 130. The control unit 120 may transmit the information stored in the memory unit 130 to the exterior (e.g., other communication devices) via the communication unit 110 through a wireless/wired interface or store, in the memory unit 130, information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit 110).

The additional components 140 may be variously configured according to types of wireless devices. For example, the additional components 140 may include at least one of a power unit/battery, input/output (I/O) unit, a driving unit, and a computing unit. The wireless device may be implemented in the form of, without being limited to, the robot (1010 a of FIG. 21), the vehicles (1010 b-1 and 1010 b-2 of FIG. 21), the XR device (1010 c of FIG. 21), the hand-held device (1010 d of FIG. 21), the home appliance (1010 e of FIG. 21), the IoT device (1010 f of FIG. 21), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medicine device, a fintech device (or a finance device), a security device, a climate/environment device, the AI server/device (400 of FIG. 21), the BSs (1020 of FIG. 21), a network node, etc. The wireless device may be used in a mobile or fixed place according to a use-example/service.

In FIG. 22, the entirety of the various elements, components, units/portions, and/or modules in the wireless devices 100 and 100 may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 100, the control unit 120 and the communication unit 110 may be connected by wire and the control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. Each element, component, unit/portion, and/or module within the wireless devices 100 and 100 may further include one or more elements. For example, the control unit 120 may be configured by a set of one or more processors. As an example, the control unit 120 may be configured by a set of a communication control processor, an application processor, an Electronic Control Unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory 130 may be configured by a Random Access Memory (RAM), a Dynamic RAM (DRAM), a Read Only Memory (ROM)), a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.

Portable Device Example to which Disclosure is Applied

FIG. 25 illustrates a portable device applied to the present disclosure. The portable device may include a smart phone, a smart pad, a wearable device (e.g., a smart watch, a smart glass), and a portable computer (e.g., a notebook, etc.). The portable device may be referred to as a Mobile Station (MS), a user terminal (UT), a Mobile Subscriber Station (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), or a Wireless terminal (WT).

Referring to FIG. 25, a portable device 1010 may include an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140 a, an interface unit 140 b, and an input/output unit 140 c. The antenna unit 108 may be configured as a part of the communication unit 110. The blocks 110 to 130/140 a to 140 c correspond to the blocks 110 to 130/140 of FIG. 24, respectively.

The communication unit 110 may transmit/receive a signal (e.g., data, a control signal, etc.) to/from another wireless device and eNBs. The control unit 120 may perform various operations by controlling components of the portable device 1010. The control unit 120 may include an Application Processor (AP). The memory unit 130 may store data/parameters/programs/codes/instructions required for driving the portable device 1010. Further, the memory unit 130 may store input/output data/information, etc. The power supply unit 140 a may supply power to the portable device 1010 and include a wired/wireless charging circuit, a battery, and the like. The interface unit 140 b may support a connection between the portable device 1010 and another external device. The interface unit 140 b may include various ports (e.g., an audio input/output port, a video input/output port) for the connection with the external device. The input/output unit 140 c may receive or output a video information/signal, an audio information/signal, data, and/or information input from a user. The input/output unit 140 c may include a camera, a microphone, a user input unit, a display unit 140 d, a speaker, and/or a haptic module.

As one example, in the case of data communication, the input/output unit 140 c may acquire information/signal (e.g., touch, text, voice, image, and video) input from the user and the acquired information/signal may be stored in the memory unit 130. The communication unit 110 may transform the information/signal stored in the memory into the radio signal and directly transmit the radio signal to another wireless device or transmit the radio signal to the eNB. Further, the communication unit 110 may receive the radio signal from another wireless device or eNB and then reconstruct the received radio signal into original information/signal. The reconstructed information/signal may be stored in the memory unit 130 and then output in various forms (e.g., text, voice, image, video, haptic) through the input/output unit 140 c.

Here, wireless communication technology implemented in wireless devices 100 and 200 of the present disclosure may include Narrowband Internet of Things for low-power communication in addition to LTE, NR, and 6G. In this case, for example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology and may be implemented as standards such as LTE Cat NB1, and/or LTE Cat NB2, and is not limited to the name described above. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may perform communication based on LTE-M technology. In this case, as an example, the LTE-M technology may be an example of the LPWAN and may be called various names including enhanced Machine Type Communication (eMTC), and the like. For example, the LTE-M technology may be implemented as at least any one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-Bandwidth Limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and/or 7) LTE M. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may includes at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering the low-power communication, and is not limited to the name described above. As an example, the ZigBee technology may generate personal area networks (PAN) associated with small/low-power digital communication based on various standards including IEEE 802.15.4, and the like, and may be called various names.

The embodiments described above are implemented by combinations of components and features of the present disclosure in predetermined forms. Each component or feature should be considered selectively unless specified separately. Each component or feature may be carried out without being combined with another component or feature. Moreover, some components and/or features are combined with each other and may implement embodiments of the present disclosure. The order of operations described in embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced by corresponding components or features of another embodiment. It is apparent that some claims referring to specific claims may be combined with another claims referring to the claims other than the specific claims to constitute the embodiment or add new claims by means of amendment after the application is filed.

Embodiments of the present disclosure may be implemented by various means, for example, hardware, firmware, software, or combinations thereof. When embodiments are implemented by hardware, one embodiment of the present disclosure may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and the like.

When embodiments are implemented by firmware or software, one embodiment of the present disclosure may be implemented by modules, procedures, functions, etc. Performing functions or operations described above. Software code may be stored in a memory and may be driven by a processor. The memory is provided inside or outside the processor and may exchange data with the processor by various well-known means.

It is apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from essential features of the present disclosure. Accordingly, the aforementioned detailed description should not be construed as limiting in all aspects and should be considered as illustrative. The scope of the present disclosure should be determined by rational construing of the appended claims, and all modifications within an equivalent scope of the present disclosure are included in the scope of the present disclosure.

INDUSTRIAL AVAILABILITY

Although the method of transmitting and receiving data in the wireless communication system of the present disclosure has been described in connection with examples in which it applies to 3GPP LTE/LTE-A system and 5G systems (new RAT systems), the method is also applicable to other various wireless communication systems. 

The invention claimed is:
 1. A method for receiving, by a user equipment (UE), downlink data in a wireless communication system, the method comprising: receiving configuration information, wherein a repetition scheme based on time division multiplexing (TDM) is configured based on the configuration information; receiving downlink control information (DCI), wherein the DCI includes a time domain resource assignment field; and receiving a plurality of transmission occasions which are related to the same transport block, based on the DCI, wherein time domain resource assignment for a first transmission occasion among the plurality of transmission occasions is determined based on the time domain resource assignment field of the DCI, and wherein time domain resource assignment for a second transmission occasion among the plurality of transmission occasions is determined based on the time domain resource assignment for the first transmission occasion.
 2. The method of claim 1, wherein a size of a second resource in a time domain for the second transmission occasion is determined based on a size of a first resource in the time domain for the first transmission occasion, and wherein the size of the second resource is determined to be equal to the size of the first resource.
 3. The method of claim 2, wherein the first resource and the second resource are constituted based on a unit of 2, 4, or 7 OFDM symbols.
 4. The method of claim 2, wherein a first symbol of the second resource is located to be apart from a last symbol of the first resource as a specific number of symbols.
 5. The method of claim 4, further comprising: receiving information on the specific number of symbols.
 6. The method of claim 2, wherein the first resource and the second resource are positioned in concatenation with each other in the time domain.
 7. The method of claim 1, wherein the DCI further includes a transmission configuration indication (TCI) field, wherein, based on that two TCI states are indicated by the TCI field, the number of the plurality of transmission occasions is determined as two.
 8. The method of claim 7, wherein a first TCI state among the two TCI states is related to the first transmission occasion and a second TCI state among the two TCI states is related to the second transmission occasion.
 9. The method of claim 1, wherein the first transmission occasion is received in one slot and the second transmission occasion is received in one slot identical to the one slot in which the first transmission occasion is received.
 10. The method of claim 1, wherein the DCI further includes a redundancy version (RV) field, and wherein an RV value of the first transmission occasion is configured to be different from an RV value of the second transmission occasion, based on the RV field.
 11. A user equipment (UE) for receiving downlink data in a wireless communication system, the UE comprising: one or more transceivers; one or more processors; and one or more memories storing instructions for operations executed by the one or more processors and connected to the one or more processors, wherein the operations include receiving configuration information, wherein a repetition scheme based on time division multiplexing (TDM) is configured based on the configuration information, receiving downlink control information (DCI), wherein the DCI includes a time domain resource assignment field, and receiving a plurality of transmission occasions which are related to the same transport block, based on the DCI, wherein time domain resource assignment for a first transmission occasion among the plurality of transmission occasions is determined based on the time domain resource assignment field of the DCI, and wherein time domain resource assignment for a second transmission occasion among the plurality of transmission occasions is determined based on the time domain resource assignment for the first transmission occasion.
 12. The UE of claim 11, wherein a size of a second resource in a time domain for the second transmission occasion is determined based on a size of a first resource in the time domain for the first transmission occasion, and wherein the size of the second resource is determined to be equal to the size of the second resource.
 13. The UE of claim 12, wherein the first resource and the second resource are positioned in concatenation with each other in the time domain.
 14. The UE of claim 11, wherein the DCI further includes a transmission configuration indication (TCI) field, wherein, based on that two TCI states are indicated by the TCI field, the number of the plurality of transmission occasions is determined as two.
 15. The UE of claim 14, wherein a first TCI state among the two TCI states is related to the first transmission occasion and a second TCI state among the two TCI states is related to the second transmission occasion.
 16. A method for transmitting, by a base station (BS), downlink data in a wireless communication system, the method comprising: transmitting, to a user equipment (UE), configuration information, wherein a repetition scheme based on time division multiplexing (TDM) is configured based on the configuration information; transmitting, to the UE, downlink control information (DCI), wherein the DCI includes a time domain resource assignment field, and transmitting, to the UE, a plurality of transmission occasions which are related to the same transport block based on the DCI, wherein time domain resource assignment for a first transmission occasion among the plurality of transmission occasions is determined based on the time domain resource assignment field of the DCI, and wherein time domain resource assignment for a second transmission occasion among the plurality of transmission occasions is determined based on the time domain resource assignment for the first transmission occasion. 